From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: -i and -o options for iptables FORWARD chain
Date: Fri, 2 Jan 2004 13:08:16 +0000 [thread overview]
Message-ID: <200401021308.16360.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <009a01c3cff6$ee23bd90$a5bbd00c@issaquah>
On Wednesday 31 December 2003 11:36 pm, Gongya Yu wrote:
> Hi, I just updated Linux kernel to 2.6.0 with iptables and ebtables
> enabled.
>
> 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.
>
> Any suggestions ?
I am not a 2.6 expert by any means, so this is just a suggestion: did you
recompile the userspace tools (iptables) to match the new kernel code
(netfilter)?
Antony.
--
My New Year's resolution is not to make any resolutions I can't keep.
I'm wondering whether I've failed already.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-01-02 13:08 UTC|newest]
Thread overview: 5+ 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 [this message]
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=200401021308.16360.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