From: Alexander Samad Date: Tue, 16 Aug 2005 08:39:38 +0000 Subject: Re: [LARTC] Multipath Routing.. Message-Id: <20050816083938.GE20254@samad.com.au> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============0231631739==" List-Id: References: <4301676E.4070100@cyberdoc.dk> In-Reply-To: <4301676E.4070100@cyberdoc.dk> To: lartc@vger.kernel.org --===============0231631739== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TD8GDToEDw0WLGOL" Content-Disposition: inline --TD8GDToEDw0WLGOL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 16, 2005 at 06:11:26AM +0200, Daniel Frederiksen wrote: > Ok folks, here goes.. >=20 > I have been boggling with a problem for the past week, and still haven't= =20 > found a solution.. >=20 > I'm trying to route traffic from two providers through a Linux machine. > But that is not the problem. The ISP's have provided me with a WAN IP=20 > class for both of the lines, to be routed into a DMZ where the machines= =20 > a to respond to their respective designated WAN IP on both lines. > Every machine on the DMZ has two IP's one on each ISP WAN Class. >=20 > I think I'll better draw a map: >=20 >=20 > WAN1(eth2), WAN2(eth3) > --------- (eth0) > | |-----\ ---------- > | DMZ |---\ \ /---| ISP1 |----- > --------- \ \ / ---------- \ > \ \ / \ > ----------------- > | Linux GW/FW | WWW > ----------------- > / \ (eth1) / > --------- / \ ---------- / > | LAN |---/ \---| ISP2 |----- > --------- ---------- > NAT(eth4) >=20 >=20 > The DMZ has two WAN IP classes routed from the ISP. >=20 > The thing I just can not figure out is how to make the respective WAN IP= =20 > from the DMZ route out the right ISP link, and the right request from=20 > the ISP route into the DMZ. >=20 > .. and finally how can I make the LAN able to access it all.. you need to use ip ru my ip ru looks like=20 0: from all lookup local=20 200: from 141.168.16.16 lookup cable=20 201: from 220.233.15.63 lookup adsl=20 32766: from all lookup main=20 32767: from all lookup default=20 I created 200 and 201 which means that all traffic that came in on the cable 141.168.16.16 will go out the cable ip ro sh tab cable 192.168.11.0/24 dev br0 scope link=20 192.168.10.0/24 dev eth3 scope link=20 192.168.9.0/24 dev eth4 scope link=20 default via 141.168.16.1 dev eth0 src 141.168.16.16 metric 30=20 and the routing tab for the adsl uses the adsl as its default gw. does that help ? >=20 > Thanks for your time.. >=20 > /Daniel Frederiksen >=20 > _______________________________________________ > LARTC mailing list > LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc >=20 --TD8GDToEDw0WLGOL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDAaZJkZz88chpJ2MRAq5hAJ9Wpi2iZmPJbM1AgEjAPpxRQ43aIACaAtbd Q6TQqOv227itEVUsngDE2Zg= =VQ8L -----END PGP SIGNATURE----- --TD8GDToEDw0WLGOL-- --===============0231631739== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc --===============0231631739==--