From: "Hansa" <mythtv@logic-q.nl>
To: 'Andrew Beverley' <andy@andybev.com>
Cc: netfilter@vger.kernel.org
Subject: RE: Is the current firewall model static?
Date: Wed, 21 Dec 2011 11:16:07 +0100 [thread overview]
Message-ID: <000001ccbfc9$8e14a0b0$aa3de210$@nl> (raw)
In-Reply-To: <1324459648.4269.83.camel@steve-pc>
On Wed, 2011-12-21 at 10:27 +0100, Andrew Beverley wrote:
> On Wed, 2011-12-21 at 10:18 +0100, Hansa wrote:
> > > I think that what they mean is that the current *Fedora* firewall model
> > > is static. It looks like firewalld still uses iptables, but is slightly
> > > more intelligent as to how it processes changes to rules and so on.
> >
> > I wasn't aware the firewall model is implemented differently across
> > different Linux flavors. I thought netfilter implements a packet
> > filtering framework into the Linux kernel. Shouldn't it work the work
> > the same on every Linux flavor?
>
> Once the iptables binary has been called and the rules have been set,
> then yes, it's the same across any flavour of Linux (I guess).
>
> I meant that the distro's implementation of how the rules are managed is
> different. There are loads of different ways. A quick search on a Ubuntu
> system reveals the following. I'm guessing that all of these use
> iptables, but some are better than others at changing rules "on the
> fly".
So it's all about 'how' the firewall is managed (by which tools that is). Netfilter by itself isn't static. Using iptables you can change the firewall dynamically. Using system-config-firewall you're static.
Thanks for clarifying!
-Hansa
next prev parent reply other threads:[~2011-12-21 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 9:25 Is the current firewall model static? Hansa
2011-12-20 10:11 ` Andrew Beverley
2011-12-21 9:18 ` Hansa
2011-12-21 9:27 ` Andrew Beverley
2011-12-21 10:16 ` Hansa [this message]
2011-12-21 10:22 ` Andrew Beverley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000001ccbfc9$8e14a0b0$aa3de210$@nl' \
--to=mythtv@logic-q.nl \
--cc=andy@andybev.com \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).