All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Victor Wren" <vwren@timension.com>
To: netfilter@lists.netfilter.org
Subject: Re: AW: a NAT question
Date: Fri, 16 Jul 2004 12:39:13 -0800	[thread overview]
Message-ID: <40F7CC71.20447.7EDE11@localhost> (raw)
In-Reply-To: <20040716185022.GA20595@tranquility.scriptkitchen.com>

> On Fri, Jul 16, 2004 at 11:43:05AM -0700, Daniel Chemko wrote:
> 
> > The setup of a Script-only setup isn't too hard. You have to abandon the
> > concept of ip aliases since netfilter dropped support for the concept.
> > You only deal with the root interface and ip addresses.
> 
> You mean the something like eth0:1 isn't supported? Do I have to
> learn the ip thing instead of ifconfig?
> For a while I would prefer ifconfig.

It's not as bad as all that, and it's really sound policy, If you think about 
it.  It's matching packets that come into a particular physical interface.  
It doesn't care what the ip address of that port is, or whether it has one 
address or twenty, so when you say "-i eth0" (or -o) just remember that 
you're also catching "eth0:56, eth0:fred, eth0:arf" etc.

I like this way of doing it.  Having the filter match aliases just mudies the 
water (and frankly, they'll all arp to the same ethernet mac address, so 
what's the point?)  If you really want to match on a particular address (or 
subnet), you can still do that with the "-d " switch.

Victor Wren



  parent reply	other threads:[~2004-07-16 20:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-16 18:43 AW: a NAT question Daniel Chemko
2004-07-16 18:50 ` Payal Rathod
2004-07-16 19:25   ` Antony Stone
2004-07-16 20:39   ` Victor Wren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-15 11:26 Account fur Maillinglisten
2004-07-16  8:51 ` Micha Silver
2004-07-16 17:55   ` Payal Rathod

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=40F7CC71.20447.7EDE11@localhost \
    --to=vwren@timension.com \
    --cc=netfilter@lists.netfilter.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 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.