<html><head></head><body>Firewalld will also tinker with forwarding and interface with the networking stack. It couples with networkmanager (command line stuff) to provide (eventually) a consistent admin interface to all things networking.<br><br>I do tend to push boundaries :-)<br><br><div class="gmail_quote">On January 27, 2019 12:18:28 PM EST, Alex Carver via Ale <ale@ale.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Perhaps but it seems like overkill to have a Python script (at the<br>moment I'm overlooking the imposed need to run an interpreter on your<br>firewall) managing iptables when, according to the documentation, any<br>rule that isn't a very simple one has to use what firewalld calls "rich<br>rules" which look exactly like a more verbose version of an iptables<br>command. It seems if you're going to have to issue a command that looks<br>just like an iptables command then why not cut the middleman and run<br>iptables? It already shows in the flow chart that it's just a wrapper<br>to iptables anyway (no direct access to the kernel).<br><br>On 2019-01-27 09:07, DJ-Pfulio via Ale wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">firewalld is just another interface into the Linux kernel firewall, just<br>like iptables or ufw.<br><br>New things take time to mature. It will get there, but that takes time.<br></blockquote><hr>Ale mailing list<br>Ale@ale.org<br><a href="https://mail.ale.org/mailman/listinfo/ale">https://mail.ale.org/mailman/listinfo/ale</a><br>See JOBS, ANNOUNCE and SCHOOLS lists at<br><a href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a><br></pre></blockquote></div><br>-- <br>Sent from my Android device with K-9 Mail. All tyopes are thumb related and reflect authenticity.</body></html>