From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: [despammed] -i and -o options for iptables FORWARD chain
Date: Fri, 2 Jan 2004 14:03:02 +0000 [thread overview]
Message-ID: <200401021403.02171.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <20040102133002.GA6057@kaufbach.delug.de>
On Friday 02 January 2004 1:30 pm, Andreas Kretschmer wrote:
> am Wed, dem 31.12.2003, um 15:36:34 -0800 mailte Gongya Yu folgendes:
> > Hi, I just updated Linux kernel to 2.6.0 with iptables and ebtables
> > enabled.
>
> I'm using iptables on 2.4.x, possible there are differences with 2.6.x.
>
> > But iptables ignores -i and -o options for FORWARD chain. Wheneneve I use
> > something like -i eth0 or -o eth0, the rule is just ignored.
>
> RTFM!
>
> -i is only for INPUT, FORWARD and PREROUTING
> -o is only for FORWARD, OUTPUT and POSTROUTING
Are you suggesting that -i and -o cannot be used in FORWARD? As far as I can
see the syntax of the rule Gonya posted is perfectly okay.
Antony.
--
Christmas is an opportunity to upgrade to kernel 2.6 while no-one's around to
notice the downtime.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-01-02 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 23:36 -i and -o options for iptables FORWARD chain Gongya Yu
2004-01-02 13:08 ` Antony Stone
2004-01-02 13:30 ` [despammed] " Andreas Kretschmer
2004-01-02 14:03 ` Antony Stone [this message]
2004-01-02 14:25 ` Andreas Kretschmer
-- strict thread matches above, loose matches on Subject: below --
2004-01-02 15:13 bmcdowell
2004-01-02 15:21 ` Andy Loukes
2004-01-02 16:05 ` Unknown, Alistair Tonner
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=200401021403.02171.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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