All of lore.kernel.org
 help / color / mirror / Atom feed
From: Menno Smits <menno@netboxblue.com>
To: Sven Schuster <schuster.sven@gmx.de>
Cc: Netfilter Mailing list <netfilter@lists.netfilter.org>
Subject: Re: Per-client routing, plus masquerading -- possible?
Date: Mon, 27 Mar 2006 16:13:07 +1000	[thread overview]
Message-ID: <44278273.3040609@netboxblue.com> (raw)
In-Reply-To: <20060323122344.GA1302@zion.homelinux.com>

Sven Schuster wrote:

> try
> 
> iptables -L -v
> 
> this will give you additional information about your rules!

Yep. -x and -n are also quite useful when viewing your configuration. 
"man iptables" is your friend.

> I don't think iptables checks if the interface exists on rule
> insertion time. Which makes sense in my opinion, so you can add
> rules e.g. for device ppp0 (or even all devices beginning with 'ppp'
> as expressed by 'ppp+') before the specific device has been created.

Agreed. Being able to insert rules for non-existent interfaces is 
definitely desirable and by design. It means rules can be in place 
before an interface comes up or even exists. This is highly useful from 
a security perspective and also provides flexibility about when you set 
up your firewall.

Menno




Scanned by the NetBox from NetBox Blue
(http://netboxblue.com/)






  reply	other threads:[~2006-03-27  6:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23  3:10 Per-client routing, plus masquerading -- possible? Jeremy Elson
2006-03-23  7:35 ` Menno Smits
2006-03-23  9:35   ` Jeremy Elson
2006-03-23 12:23     ` Sven Schuster
2006-03-27  6:13       ` Menno Smits [this message]
2006-03-23 13:46 ` Steven M Campbell

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=44278273.3040609@netboxblue.com \
    --to=menno@netboxblue.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=schuster.sven@gmx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.