News for hackers. Stuff that matters.
Re:OpenBSD PF versus FreeBSD PF by gigatexal on Wednesday September 27, 2023 @03:52PM (#37680305)
But don’t have to cobble together a bunch of arcane iptables commands and then combine bpf and other userland tools … when one can just use the clean syntax of PF especially for home use that’s a clear win.
Re:OpenBSD PF versus FreeBSD PF by ADSSDA on Wednesday September 27, 2023 @03:57PM (#37680390)
I've used both extensively and I find eBPF+iptables (and sometimes nft) significantly more flexible and easier to use in the real world (not just simple examples) than PF. shrug
Re:OpenBSD PF versus FreeBSD PF by gigatexal on Wednesday September 27, 2023 @06:07PM (#37682047)
Do you have a sample or blogpost of how your setup looks? I’m keen to see how folks are using eBPF in the personal firewall space
Re:OpenBSD PF versus FreeBSD PF by throw0101a on Wednesday September 27, 2023 @04:46PM (#37681075)
> But don’t have to cobble together a bunch of arcane iptables commands

If you did manage to figure out the iptables commands you now have to change them over to nftables. :)

Re:OpenBSD PF versus FreeBSD PF by carlhjerpe on Wednesday September 27, 2023 @05:56PM (#37681916)
No, iptables is a perfectly functional nftables frontend
Re:OpenBSD PF versus FreeBSD PF by systems_glitch on Wednesday September 27, 2023 @05:01PM (#37681244)
Not having to manage two rulesets -- one for IPv4 and one for IPv6 -- is pretty well a killer feature in my mind.
Re:OpenBSD PF versus FreeBSD PF by nolist_policy on Wednesday September 27, 2023 @05:25PM (#37681549)
nftables is now almost 10 years old! It's time to forget the bad experiences with iptables.
Re:OpenBSD PF versus FreeBSD PF by systems_glitch on Wednesday September 27, 2023 @10:09PM (#37684328)
I have -- I let the OpenBSD firewalls take care of it :P

Seriously though it's something I need to get familiar with, I do still have plenty of Linux boxes that face the public Internet and are currently dependent on iptables/ip6tables rulesets. The problem is I'm currently masking that pain with Ansible.