From: Chris Brenton <cbrenton@chrisbrenton.org>
To: Antony Stone <Antony@Soft-Solutions.co.uk>
Cc: netfilter@lists.netfilter.org
Subject: Re: using iptables to route between public networks
Date: Tue, 23 Dec 2003 12:16:39 -0500 [thread overview]
Message-ID: <1072199798.3572.470.camel@grendel> (raw)
In-Reply-To: <200312231542.48587.Antony@Soft-Solutions.co.uk>
I replied to Matthew off-list on this one. Note the last two lines. "It
works" because he sets a default ACCEPT policy and then flushes the
previous rules.
You are right about the syntax on the first two lines, but iptables is
smart enough to correct it and implements 209.210.10.0/28.
C
On Tue, 2003-12-23 at 10:42, Antony Stone wrote:
> On Tuesday 23 December 2003 3:32 pm, Matthew Simpson wrote:
>
> > I must have been doing something stupid last night, because I retried it
> > this morning and it works. Here is what I have for the forward chain:
> >
> > $IPTABLES -A FORWARD -d 209.210.10.1/28 -j ACCEPT
> > $IPTABLES -A FORWARD -d ! 209.210.10.1/28 -j DROP
> > $IPTABLES -P FORWARD ACCEPT
> > $IPTABLES -F FORWARD
> >
> > This works.
>
> When you say "this works", is assume that's only for minimal values of
> "working" :)
>
> I can't believe that a router which will drop all packets except those
> addressed to 209.210.10.0/28 (note that your address designation is slightly
> incorrect above) will do an effective job.
>
> You may want to route inbound packets only to these IP addresses, but what
> about the replies? They are going to be going to other destination
> addresses, and need routing too.....
>
> Antony.
next prev parent reply other threads:[~2003-12-23 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 15:32 using iptables to route between public networks Matthew Simpson
2003-12-23 15:42 ` Antony Stone
2003-12-23 17:16 ` Chris Brenton [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-23 17:24 Matthew Simpson
2003-12-23 9:09 Antony Stone
2003-12-23 4:30 Matthew Simpson
2003-12-23 10:53 ` Chris Brenton
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=1072199798.3572.470.camel@grendel \
--to=cbrenton@chrisbrenton.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.