From: Peter Surda <surda@shurdix.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Firewall.routing configuration problems
Date: Thu, 20 Oct 2005 17:03:29 +0000 [thread overview]
Message-ID: <20059201932925342@mail.routehat.org> (raw)
In-Reply-To: <003c01c5d595$00853360$e7544381@SANNPJLTABLET>
On Thu, 20 Oct 2005 17:40:38 +0100 "Paul Lewis"
<paul.lewis@st-annes.oxford.ac.uk> wrote:
>Hi,
hi
[cut]
>The students go out onto an academic connection (via
>eth0), and conference guests go out on an ADSL line (via eth3). eth1 and
>eth2 are configured for internal use.
ok.
>The firewall rules
>for routing packets to the correct ethernet device (conference guests to
>eth3 and students to eth0) are as follows:
> iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j MASQUERADE -o
>eth3
[cut]
You are mistaken here I think. This doesn't influence routing, only
masquerading. You are problably missing (in addition to what you have) policy
based routing, something like:
ip rule add from 192.168.0.0/22 table 10
ip rule add from 192.168.4.0/22 table 11
ip route add default via your_gateway_on_eth3 dev eth3 table 10
ip route add default via your_gateway_on_eth0 dev eth0 table 11
(in reality it is slightly more complicated, you need to add proper routes for
other subnets if you want them to be able to communicate with each other).
>Many thanks,
>
>Paul
Yours sincerely,
Peter
--
http://www.shurdix.org - Linux distribution for routers and firewalls
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-10-20 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 16:40 [LARTC] Firewall.routing configuration problems Paul Lewis
2005-10-20 16:40 ` Paul Lewis
2005-10-20 17:03 ` Peter Surda [this message]
2005-10-20 19:17 ` /dev/rob0
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=20059201932925342@mail.routehat.org \
--to=surda@shurdix.com \
--cc=lartc@vger.kernel.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.