From: Alex Samad Date: Mon, 29 Jan 2007 21:35:40 +0000 Subject: Re: [LARTC] Questions about mutiple providers Message-Id: <20070129213540.GJ25822@samad.com.au> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============1758392934==" List-Id: References: <615095102.20070129131703@kurgan.org> In-Reply-To: <615095102.20070129131703@kurgan.org> To: lartc@vger.kernel.org --===============1758392934== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1y6imfT/xHuCvpN0" Content-Disposition: inline --1y6imfT/xHuCvpN0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 29, 2007 at 01:17:03PM +0100, Fabio Muzzi wrote: >=20 > Hi, this is my first post to the list. >=20 > I have googled a lot, and still cannot find a proper solution. I hope > someone here will be able to shed some light on my doubts. >=20 > I have set up a firewall using kernel 2.6.15 (Debian) that does NAT for > 100 clients, and uses two different ISPs, using the howto found at > http://lartc.org/howto/lartc.rpdb.multiple-links.html. I have *not* > patched my kernel. >=20 > The rounting setup is taken from the howto, and it basically works, I see > packets flowing out of both WAN interfaces, and everyting seems to work > properly for packets that are generated from the firewall itself. >=20 > I have set up NAT rules in postrouting table, this way: >=20 > iptables -t nat -A POSTROUTING -o $WAN -j SNAT -s 10.0.0.0/16 --to-sourc= e 217.221.234.74 > iptables -t nat -A POSTROUTING -o $WAN2 -j SNAT -s 10.0.0.0/16 --to-sourc= e 83.211.205.162 >=20 > Local net is 10.0.0.0/16, the two WAN interfaces are $WAN and $WAN2, and > their relative IP addresses are set as shown. WAN interfaces are > phisically different and have no aliases, only the IP shown above. >=20 > Now, I am experiencing two issues: >=20 > - First, I see packets with "from" address set to 83.211.205.162 that go > out of $WAN, and also packets with from address set to 217.221.234.74 that > flow out of $WAN2. This address mixup should not happen, I suppose. > looking at the packets, it seems that only NATed trafic shows this > behaviour. you have to setup your ip rule rules, which will state anything coming from 217.221.234.74 only goes out $WAN and anything coming from 83.211.205.162 o= nly goes out $WAN2, it should be part of the wiki/faq doco >=20 >=20 > - Second, I see (rare) packets flowing out of WAN or WAN2 interfaces that > still have the LAN from address, that is 10.0.x.x, these packets somehow > where not NATed at all. never seen this >=20 >=20 > Now, the questions are: >=20 > How do I solve this? >=20 > Do I need to patch my kernel to solve the first issue, because I need to > lock at NAT "established connections" tables to make routing decisions? Is > it impossible to have equal cost multipath and SNAT together without > patching the kernel? If so, what patch do I need exactly? >=20 > Is there something wrong with my kernel version, that has a broken NAT > support? (this could explain why I get some packets that do not get NATed > at all) >=20 >=20 > Thanks a lot for the time you took reading this. >=20 > --=20 >=20 > Fabio "Kurgan" Muzzi >=20 > _______________________________________________ > LARTC mailing list > LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc >=20 --1y6imfT/xHuCvpN0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFvmiskZz88chpJ2MRAgg2AKCz9YW8uj95K+XjhXGHxoMQZ2udxgCgiQJi yvVXy2MPMjmXhhHWShsIvh8= =yW1T -----END PGP SIGNATURE----- --1y6imfT/xHuCvpN0-- --===============1758392934== 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 --===============1758392934==--