From: Andy Loukes <andy@navaho.co.uk>
To: bmcdowell@coxhealthplans.com
Cc: netfilter@lists.netfilter.org
Subject: RE: [despammed] -i and -o options for iptables FORWARD chain
Date: Fri, 2 Jan 2004 15:21:48 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.58.0401021520440.4138@picea.navaho> (raw)
In-Reply-To: <7A3B4AA360FDEF448F3390421FC8D731012C6B04@coxhpexg.coxhp.com>
On Fri, 2 Jan 2004 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.
No, the physdev stuff is for bridging. -i and -o work the same in 2.6 as
2.4
--
Andy Loukes
http://www.navaho.co.uk Complete Appliance Technology
next prev parent reply other threads:[~2004-01-02 15:21 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 [this message]
2004-01-02 16:05 ` Unknown, Alistair Tonner
-- 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=Pine.LNX.4.58.0401021520440.4138@picea.navaho \
--to=andy@navaho.co.uk \
--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