don/www.duckland.org
1
0
Fork 0
Code Issues Pull requests Releases Activity

new post: firewall saga pt ii

Browse source
This commit is contained in:
Don Harper 2021-03-22 20:39:44 -05:00
parent 2d4d52a38d
commit 130c058172
2 changed files with 17 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

17
content/post/2021/03/firewall-saga-pt-ii.md Normal file
View file

@ -0,0 +1,17 @@
---
date: "2021-03-21T04:00:00-07:00"
title: "Firewall Saga, pt II"
categories: ["personal", "sa"]
image: "/images/ipfire-tux.png"
featured_image: "/images/ipfire-tux.png"
#series: [""]
summary: "The saga continues"
Victor_Hugo: "true"
Focus_Keyword: "firewall"
meta: "The firewall saga continues"
---
When I was here [last]({{< ref "/post/2021/03/crash-of-the-firewall.md">}}), I was talking about how my trusty firewall appliance of many years had fallen over, and the challenges of trying to get [pfSense](https://www.pfsense.org) working on the new hardware. I figured it was time for a quick updates.
This last weekend, I did cut over to the purpose-bought box for the firewall, but I have not as of yet put to use the extra ports for WiFi and DMZ use. I still have a bit of thinking to do on how I best want to set that up.
Whilst I am not pleased to find out the IPFire team's thoughts on [wireguard](https://blog.ipfire.org/post/why-not-wireguard), I respect their decision on their project. Given that I am currently running wireguard at home (I have not had a chance to test it outside yet due to the [plague](/tags/plague)) I was hoping they would support it. As if the fact I could not get pfSense booting was not reason enough, the pfSense project announced that they were dropping support for wireguard for the foreseeable future.