17 lines
1.3 KiB
Markdown
17 lines
1.3 KiB
Markdown
---
|
|
date: "2021-03-21T04:00:00-07:00"
|
|
title: "Firewall Saga, pt II"
|
|
categories: ["personal", "sa"]
|
|
image: "/images/ipfire-tux.webp"
|
|
featured_image: "/images/ipfire-tux.webp"
|
|
#series: [""]
|
|
summary: "The saga continues"
|
|
Victor_Hugo: "true"
|
|
Focus_Keyword: "firewall"
|
|
meta: "The firewall saga continues"
|
|
---
|
|
When I was here [last]({{<ref "crash-of-the-firewall">}}), 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/posts/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.
|