On 9/14/2019 10:03 AM, Bruce Dubbs via blfs-dev wrote:
On 9/14/19 12:46 AM, DJ Lucas via blfs-dev wrote:


On 9/13/2019 7:32 PM, Bruce Dubbs via blfs-dev wrote:
On 9/13/19 5:52 PM, DJ Lucas via blfs-dev wrote:
Subject says it all. It changed sometime between 6.2.0 and 6.3, but nobody noticed the issue on the firewall page. It read well enough I guess, though it's painfully obvious that it is wrong now. Other examples in the book work as expected. Fortunately, this is the only page in the book where this syntax was used.

That's interesting.  Checking, what we have is valid docbook xml. It must be something in our stylesheets.


I'm planning on overhauling this page soon anyway, just providing an introduction and pointing to the iptables and nftables pages where the actual configuration is done and supplying the sect3 title.

That would be good.  Thanks.

Here is a *very* preliminary patch of that work. I'd appreciate any feedback and suggestions for text/configurations. I haven't tested the changes (the additions are incomplete for the masquerading example for iptables). If anybody has done the other two examples for nftables, or has used firewalld, please post simple samples.

http://www.linuxfromscratch.org/~dj/blfs-book/
http://www.linuxfromscratch.org/~dj/blfs-systemd/
http://www.linuxfromscratch.org/~dj/add-nftables.svnstash

It's been a *very* long time since I looked at the firewall rules.

Why are we using ppp for the interface parameters?  That seems to be last century.  Shouldn't it be eth+ or similar?


Yeah, I thought about throwing in a udev rule for WAN/LAN ifnames but decided against it. Not that I do it all the time, but for my two dedicated firewalls, I rename the interfaces so that the configuration is explicit. That said, we don't cover it in BLFS anymore, but people do still use rp-pppoe for DSL connections. I suppose we should use eth0 and eth1, or maybe better, enforce it as strictly an example by using WAN and LAN (or similar) without any udev rule in sight. I actually like how it's done in the BusyBox example, piece by piece the best, but showing it as a script is important too.

--DJ

--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to