netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: problem with forward/nat
Date: Sun, 7 Mar 2004 18:37:16 +0000	[thread overview]
Message-ID: <200403071837.16641.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <1078683840.404b68c0641ac@realdealz.ch>

On Sunday 07 March 2004 6:24 pm, Fabian Hartmann wrote:

> > hello,
>
> Hi Pierre
>
> > #forward
> >
> > iptables -A FORWARD -s 192.168.1.0/24 -j ACCEPT -o eth0
>
> The rule above won't work! you must set the -o flag before you set the -j
> <TARGET> i. e. iptables -A FORWARD -o eth0 -s 192.168.1.0/24 -j ACCEPT

My netfilter accepts it perfectly well, and afterwards "iptables -L FORWARD 
-nvx" shows:

pkts   bytes target    prot opt in     out     source              destination
   0     0 ACCEPT    all  --  *      eth0    192.168.1.0/24       0.0.0.0/0

> Otherwise the rule won't be accepted by iptables and you have no rule that
> accepts  forwarded traffic when the default policy for the FORWARD chain is
> set to DROP.

Let me know which version of netfilter you have a problem with using the above 
syntax - admittedly it's non-standard, but it seems to work okay.

Antony.

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

                                                     Please reply to the list;
                                                           please don't CC me.



      reply	other threads:[~2004-03-07 18:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-07  3:13 problem with forward/nat Pierre Gillet
2004-03-07  9:26 ` Antony Stone
2004-03-07  9:46   ` Antony Stone
2004-03-07 14:47 ` Brad Morgan
2004-03-07 15:03   ` Antony Stone
2004-03-07 15:57     ` Brad Morgan
2004-03-07 18:24 ` Fabian Hartmann
2004-03-07 18:37   ` Antony Stone [this message]

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=200403071837.16641.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;
as well as URLs for NNTP newsgroup(s).