Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I've used both and the main advantage is PF/ipfw syntax.

But now with nftables I actually am going back to RHEL on Firewalls. I want something ultra-stable and long lived.



I've been using OpenBSD and PF for nearly 25 years (PF debuted December 2001). Over those years there have been syntax changes to pf.conf, but the most disruptive were early on, and I can't remember the last syntax change that effected my configs (mostly NAT, spamd, and connection rate limiting).

During that time the firewall tool du jour on Linux was ipchains, then iptables, and now nftables, and there have been at least some incompatible changes within the lifespan of each tool.

OpenBSD has an additional leg up in that incompatible changes between releases are concisely, clearly, and consistently documented, e.g. https://www.openbsd.org/faq/upgrade78.html The last incompatible pf.conf syntax change I could find was for 6.9, nearly 5 years ago, https://www.openbsd.org/faq/upgrade69.html


You left off ipfwadm before ipchains.


And iptables has been around since 2001, and can still be used.

Alternatively you can use nftables which has only been around for the past 12 years.

I realise that one change per quarter century is possibly a little fast paced for BSD but I can cope with it.


PF is also from 2001. But its roots go further back, I once used a very PF-like syntax on a Unix firewall from 1997. I forget which type of Unix it was, maybe Solaris.

Either way, I don't think there is any defense for the strange syntax of IPtables, the chains, the tables. And that's coming from a person who transitioned fully from BSD to Linux 15 years ago, and has designed commercial solutions using IPtables and ipset.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: