From: Unknown <unknown@unknown.invalid>
From: Alistair Tonner <>
To: bmcdowell@coxhealthplans.com, netfilter@lists.netfilter.org
Subject: Re: [despammed] -i and -o options for iptables FORWARD chain
Date: Fri, 2 Jan 2004 11:05:24 -0500 [thread overview]
Message-ID: <7544.88308816708$1073059859@news.gmane.org> (raw)
In-Reply-To: <7A3B4AA360FDEF448F3390421FC8D731012C6B04@coxhpexg.coxhp.com>
On January 2, 2004 10:13 am, bmcdowell@coxhealthplans.com wrote:
> Actually, couldn't this be just a 2.6.x change? (I never saw the rules go
> by...) I thought I saw a message go by earlier to that effect. Something
> about the syntax and needing '--physdev' and '-i' both, or something?
>
> I could search the archives, I guess, but instead I suggest Gonya give that
> a go.
>
Userspace tools need to be recompiled from 2.4.x kenels to 2.6.0
I got weird results switching. Recompile fixed the problems.
Alistair
>
> Bob
> -----Original Message-----
> From: netfilter-admin@lists.netfilter.org
> [mailto:netfilter-admin@lists.netfilter.org]On Behalf Of Antony Stone
> Sent: Friday, January 02, 2004 8:03 AM
> To: netfilter@lists.netfilter.org
> Subject: Re: [despammed] -i and -o options for iptables FORWARD chain
>
> 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.
next prev parent reply other threads:[~2004-01-02 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 15:13 [despammed] -i and -o options for iptables FORWARD chain bmcdowell
2004-01-02 15:21 ` Andy Loukes
2004-01-02 16:05 ` Unknown, Alistair Tonner [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-31 23:36 Gongya Yu
2004-01-02 13:30 ` [despammed] " Andreas Kretschmer
2004-01-02 14:03 ` Antony Stone
2004-01-02 14:25 ` Andreas Kretschmer
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='7544.88308816708$1073059859@news.gmane.org' \
--to=unknown@unknown.invalid \
--cc=bmcdowell@coxhealthplans.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox