From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Samad Date: Sun, 14 Jan 2007 09:26:18 +0000 Subject: Re: [LARTC] multipath device round robin not working? Message-Id: <20070114092618.GA19650@samad.com.au> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============0037022564==" List-Id: References: <45A8C870.2010806@gmail.com> In-Reply-To: <45A8C870.2010806@gmail.com> To: lartc@vger.kernel.org --===============0037022564== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 13, 2007 at 12:54:24PM +0100, zutph3n@gmail.com wrote: > Hi, >=20 > I have a linux server running kernel 2.6.19 that is connected with 2=20 > seperate 100Mbit links to the same isp: >=20 >=20 > +---+ > +---------------+ | I | =20 > +---------------+ > | | | S | =20 > | | > | eth0 --+--------------+ P | =20 > | | > | | | S | =20 > | | > | linux 2.6.19 | | W |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D| ISP=20 > GATEWAY | > | | | I | =20 > | | > | eth1 --+--------------+ T | =20 > | | > | | | C | =20 > | | > +---------------+ | H | =20 > +---------------+ > +---+ >=20 > Both links have their own ip but have the same gateway. The problem is I= =20 > can't seem to get egress traffic load balanced over the 2 nics. >=20 > IP config after boot (dhcp from isp) > ip a: >=20 > 1: lo: mtu 16436 qdisc noqueue > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 brd 127.255.255.255 scope host lo >=20 > 2: eth0: mtu 1500 qdisc=20 > pfifo_fast qlen 1000 > link/ether 00:00:00:00:00:0f brd ff:ff:ff:ff:ff:ff > inet 10.0.0.110/24 brd 10.0.0.255 scope global eth0 >=20 > 3: eth1: mtu 1500 qdisc=20 > pfifo_fast qlen 1000 > link/ether 00:00:00:00:00:ed brd ff:ff:ff:ff:ff:ff > inet 10.0.0.120/24 brd 10.0.0.255 scope global eth1 >=20 > Default routing table after boot > ip r: >=20 > 10.0.0.0/24 dev eth0 scope link > 10.0.0.0/24 dev eth1 scope link metric 1 > 127.0.0.0/8 dev lo scope link > default via 10.0.0.1 dev eth0 > default via 10.0.0.1 dev eth1 metric 1 >=20 > I enabled ip_forward and set arp_ignore to 1 for eth0 and eth1 to make=20 > sure the correct nic answers to arp requests. >=20 > I tried to get the egress load balancing to work by replacing the above= =20 > two default routes with: >=20 > ip route add default mpath drr nexthop via 10.0.0.1 dev eth0 weight 1=20 > onlink nexthop via 10.0.0.1 dev eth1 weight 1 onlink >=20 > I assumed that with mpath device round robin both nics would be used=20 > more or less equally, but the reality is only one of the nics actually=20 > works and the second nic even stops responding to arp requests. >=20 > Am I doing something totally wrong or impossible here or is the device=20 > round robin code not working properly? Curiosity but why use such a setup is your ISP link > 2Gbp/s ? Why not bon= d if you want HA. why its not round robining. I am going to guess but this line default via 10.0.0.1 dev eth0 costs less to use than default via 10.0.0.1 dev eth1 metric 1 so it should never use the second. I say guess cause I don't know what the default metric is if you do add one. What you want it to look something like is default proto static metric 5=20 nexthop via 144.132.144.1 dev vlan2 weight 5 nexthop via 10.20.20.230 dev ppp0 weight 20 There is a link to a howto on the web site that steps out how to set this up Alex > _______________________________________________ > LARTC mailing list > LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc >=20 --0F1p//8PRICkK4MW 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) iD8DBQFFqfc6kZz88chpJ2MRAqcYAJ0e6qq+Cwys3i/Vtn6I6lYbAoltmwCfcQj5 oaW3TpAUrD2wJQlF6jgJm3s= =P0DO -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW-- --===============0037022564== 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 --===============0037022564==--