From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Iptables and Zebra
Date: Tue, 16 Dec 2003 10:21:14 +0000 [thread overview]
Message-ID: <200312161021.14594.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <006301c3c3b7$e02ef0b0$220aa8c0@BERTRAND>
On Tuesday 16 December 2003 9:34 am, Bertrand TACHAGO wrote:
> Hi to all!
> I'm trying to setup a zebra router on a RH9 machine but right I'm blocked
> because there's a firewall (iptables) problem. I had entered a POSTROUTING
> rule (iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE) but the packets
> are not routed to the external interface. Can somebody help me solve this
> problem (use zebra routing protocol to route packets from my network to the
> Internet)?
Netfilter does not route packets for you. It can change the source or
destination addresses, and it can block certain packets from being routed,
but the decision about where / how / why to route packets is not made by
netfilter.
The rule you have given above will make sure that all packets leaving
interface eth0 will have the IP address of that interface as their source
address. It does not affect in any way which packets get routed via eth0 on
their way anywhere else.
Sorry I can't be more help, but I wanted to make sure you understood that a
routing problem is not a netfilter problem.
Antony.
--
The difference between theory and practice is that in theory there is no
difference, whereas in practice there is.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2003-12-16 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 9:34 Iptables and Zebra Bertrand TACHAGO
2003-12-16 10:21 ` Antony Stone [this message]
2003-12-16 11:06 ` Ralf Spenneberg
2003-12-16 11:58 ` Bertrand TACHAGO
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=200312161021.14594.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