From: "Tóth Nándor" <nug@sch.bme.hu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] NAT over 2 providers (not load balance)
Date: Mon, 14 Feb 2005 20:47:24 +0000 [thread overview]
Message-ID: <42110E5C.5000802@sch.bme.hu> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAENEVIhFsNkiQ6vTBNVSNQcKAAAAQAAAAwP1excSwi0q2AVixPMeQJAEAAAAA@web-profile.net>
Hi!
Mihai Vlad wrote:
> Hi guys,
>
> Can you take a look at this? :)
>
>
> +-----------+
> | |
> eth1-|- |
> | -|-eth0---LAN---
> | |
> eth2-|- |
> | |
> +-----------+
> -
>
> eth0 is connected to the LAN having the IP=LAN_IP
>
> eth1 is connected to the first ISP having IP=ISP_IP_1 and GW=ISP_GW_1
> eth2 is connected to the second ISP having IP=ISP_IP_2 and GW=ISP_GW_2
>
> I need to selectively SNAT clients in the LAN to ISP_IP_1 or ISP_IP_2.
>
> That would be something like:
> $IPTABLES -t nat -A POSTROUTING -s 172.17.31.5 -j SNAT --to-source $ISP_IP_1
> $IPTABLES -t nat -A POSTROUTING -s 172.17.31.7 -j SNAT --to-source $ISP_IP_2
>
>
> This does not work since all the packets are forwarded to the default GW
> which is ISP_GW_1.
>
> How can I change this?
>
> As far as I remember, the routing decisions and policy are before the
> POSTROUTING chain in which the SNAT occurs...
$IPTABLES -t nat -A POSTROUTING -o $EXTERNAL_INTERFACE -j SNAT
--to-source $EXTERNAL_IP_ADDR
$IPTABLES -t nat -A POSTROUTING -o $EXTERNAL_INTERFACE2 -j SNAT
--to-source $EXTERNAL_IP_ADDR2
And add some rules based on client's source ip address. (policy routing)
http://www.linux.com/howtos/Adv-Routing-HOWTO/lartc.rpdb.simple.shtml
--
Udv,
Nandor
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2005-02-14 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-14 20:27 [LARTC] NAT over 2 providers (not load balance) Mihai Vlad
2005-02-14 20:35 ` Ben
2005-02-14 20:47 ` /dev/rob0
2005-02-14 20:47 ` Tóth Nándor [this message]
2005-02-14 21:58 ` Peter Surda
2005-02-14 22:19 ` Nguyen Dinh Nam
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=42110E5C.5000802@sch.bme.hu \
--to=nug@sch.bme.hu \
--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.