Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Arnt Karlsen <arnt@c2i.net>
To: netfilter@lists.netfilter.org
Subject: Re: POSTROUTING
Date: Thu, 19 Feb 2004 00:45:20 +0100	[thread overview]
Message-ID: <20040219004520.18352b71.arnt@c2i.net> (raw)
In-Reply-To: <200402181825.35022.Antony@Soft-Solutions.co.uk>

On Wed, 18 Feb 2004 18:25:34 +0000, 
Antony Stone <Antony@Soft-Solutions.co.uk> wrote in message 
<200402181825.35022.Antony@Soft-Solutions.co.uk>:

> On Wednesday 18 February 2004 6:26 pm, capsx wrote:
> 
> > !
> >
> > I want as source to specify a chain
> > not -s 10.0.0.0/27 but something like -s LOCAL_NET_CHAIN
> 
> You can't do that.   -s takes an address or network range.   -i takes
> an interface name.   You cannot specify anything else as the 'source'
> of a packet.
> 
> Tell us why you want to do this and we might be able to suggest an
> alternative 

..I suspect he means he wants " -s $LOCAL_NET " or somesuch, such
variables needs first be defined like ' LOCAL_NET="10.0.0.0/27" ', 
for larger sites, it's possible to script these definitions, check the 
http://tldp.org/LDP/abs/html/ over at http://tldp.org/guides.html for
ideas.

> (MARKing packets comes to mind, for example).

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.




  reply	other threads:[~2004-02-18 23:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-18 15:08 POSTROUTING capsx
2004-02-18 17:52 ` POSTROUTING Alexis
2004-02-18 18:07   ` POSTROUTING capsx
2004-02-18 18:14     ` R: POSTROUTING giovanni costagliola
2004-02-18 18:26       ` POSTROUTING capsx
2004-02-18 18:25         ` POSTROUTING Antony Stone
2004-02-18 23:45           ` Arnt Karlsen [this message]
2004-02-18 23:31             ` POSTROUTING Antony Stone

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=20040219004520.18352b71.arnt@c2i.net \
    --to=arnt@c2i.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox