Hi all :) there is somekind of strange Routing problem that im getting with Linux-2.6.16 and iproute 2.6.16 , when i use command like : ip route add default nexthop via 1.1.1.1 dev eth0 nexthop via 1.1.1.2 dev eth1 all packets goes on 1.1.1.2 ( always last interface ) , whats is the problem ? this situation also tested with equalize flag , on two physical interface and etc ... -- Lady Luck brings added income today. Lady friend takes it away tonight.
Hi all :) there is somekind of strange Routing problem that im getting with Linux-2.6.16 and iproute 2.6.16 , when i use command like : ip route add default nexthop via 1.1.1.1 dev eth0 nexthop via 1.1.1.2 dev eth1 all packets goes on 1.1.1.2 ( always last interface ) , whats is the problem ? this situation also tested with equalize flag , on two physical interface and etc ... -- Lady Luck brings added income today. Lady friend takes it away tonight.
El Friday 23 June 2006 06:59, Armin ranjbar escribió:> Hi all :) > > there is somekind of strange Routing problem that im getting with > Linux-2.6.16 and iproute 2.6.16 , when i use command like : > > ip route add default nexthop via 1.1.1.1 dev eth0 nexthop via 1.1.1.2 dev > eth1 > > all packets goes on 1.1.1.2 ( always last interface ) , whats is the > problem ? this situation also tested with equalize flag , on two physical > interface and etc ...Equalize was available as a patch in 2.4 kernels and AFAIK there are not 2.6 patches, so to set that flag do nothing in most cases. I think you have CONFIG_IP_ROUTE_MULTIPATH_CACHED set in your kernel(which is EXPERIMENTAL and mostly undocumented) and you''re not selecting any of the 4 multipath cache algos. Try adding ''mpath'' option to your ''tc'' command: ip route add default mpath rr nexthop via 1.1.1.1 dev eth0 nexthop via 1.1.1.2 dev eth1 If that do not work, recompile your kernel without CONFIG_IP_ROUTE_MULTIPATH_CACHED multipath will probably work at first try. Plz don''t forget to post your results to the list. -- Luciano
On Fri, 23 Jun 2006 20:04:53 -0300 Luciano Ruete <luciano@lugmen.org.ar> wrote:> > Equalize was available as a patch in 2.4 kernels and AFAIK there are not 2.6 > patches, so to set that flag do nothing in most cases. >its quite strange , its somesort of working under 2.6.16 ,> I think you have CONFIG_IP_ROUTE_MULTIPATH_CACHED set in your kernel(which is > EXPERIMENTAL and mostly undocumented) and you''re not selecting any of the 4 > multipath cache algos. Try adding ''mpath'' option to your ''tc'' command: > > ip route add default mpath rr nexthop via 1.1.1.1 dev eth0 nexthop via 1.1.1.2 > dev eth1 > > If that do not work, recompile your kernel without > CONFIG_IP_ROUTE_MULTIPATH_CACHED multipath will probably work at first try. > > Plz don''t forget to post your results to the list.my kernel compiled with : CONFIG_IP_ROUTE_MULTIPATH=y CONFIG_IP_ROUTE_MULTIPATH_CACHED=y CONFIG_IP_ROUTE_MULTIPATH_RR=y CONFIG_IP_ROUTE_MULTIPATH_RANDOM=y CONFIG_IP_ROUTE_MULTIPATH_WRANDOM=y CONFIG_IP_ROUTE_MULTIPATH_DRR=y and all of this algorithms works perfectly over icmp , but there is some (maybe) problems with tcp round robin algorithm : with : ip route add default mpath rr nexthop via 1.1.1.2 dev eth0 nexthop via 1.1.1.3 dev eth0 wget i attempt to wget a file over tcp port 80 , all packets goes to 1.1.1.2 , nothing on 1.1.1.3 . but with : ip route add default mpath random nexthop via 1.1.1.2 dev eth0 nexthop via 1.1.1.3 dev eth0 i''ve got something on 1.1.1.3 and everything goes as expected , any idea ? we have to report bug ?> > -- > Lucianothank you -- You will be aided greatly by a person whom you thought to be unimportant.
> > CONFIG_IP_ROUTE_MULTIPATH=y > CONFIG_IP_ROUTE_MULTIPATH_CACHED=y > CONFIG_IP_ROUTE_MULTIPATH_RR=y > CONFIG_IP_ROUTE_MULTIPATH_RANDOM=y > CONFIG_IP_ROUTE_MULTIPATH_WRANDOM=y > CONFIG_IP_ROUTE_MULTIPATH_DRR=y > > and all of this algorithms works perfectly over icmp , but there is some (maybe) problems with tcp round robin algorithm : > > with : > ip route add default mpath rr nexthop via 1.1.1.2 dev eth0 nexthop via 1.1.1.3 dev eth0 > wget i attempt to wget a file over tcp port 80 , all packets goes to 1.1.1.2 , nothing on 1.1.1.3 . > > but with : > ip route add default mpath random nexthop via 1.1.1.2 dev eth0 nexthop via 1.1.1.3 dev eth0 > i've got something on 1.1.1.3 and everything goes as expected , any idea ? we have to report bug ?There are some problems with the balancing code in newer kernels. As stated few days earlier removing multipath caching does help prety good. Also a side remark with one client (load) you will see almost no effect. When you load the link wih lots of connections then the balancing works. Remove multipath caching and try again If your ISP's can offer you BGP (even read only/listen) resort to it. It will do much better. -- С уважение, Владимир Витков http://www.netsecad.com http://www.supportbg.com _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
On Sun, 25 Jun 2006 21:46:06 +0300 "Vladimir Vitkov" <vvitkov@gmail.com> wrote:> Remove multipath caching and try againif i remove CONFIG_IP_ROUTE_MULTIPATH_CACHED i will be unable to use : CONFIG_IP_ROUTE_MULTIPATH_RR CONFIG_IP_ROUTE_MULTIPATH_RANDOM CONFIG_IP_ROUTE_MULTIPATH_WRANDOM CONFIG_IP_ROUTE_MULTIPATH_DRR right ? -- You will always get the greatest recognition for the job you least like.
On Monday 26 June 2006 08:28, Armin ranjbar wrote:> On Sun, 25 Jun 2006 21:46:06 +0300 > > "Vladimir Vitkov" <vvitkov@gmail.com> wrote: > > Remove multipath caching and try again > > if i remove > CONFIG_IP_ROUTE_MULTIPATH_CACHED > > i will be unable to use : > CONFIG_IP_ROUTE_MULTIPATH_RR > CONFIG_IP_ROUTE_MULTIPATH_RANDOM > CONFIG_IP_ROUTE_MULTIPATH_WRANDOM > CONFIG_IP_ROUTE_MULTIPATH_DRR > > right ?yes, this modules are also EXPERIMENTAL code, and multipath work perfectly without them. -- Luciano
On 26/06/06, Armin ranjbar <zoup@zoup.org> wrote:> On Sun, 25 Jun 2006 21:46:06 +0300 > "Vladimir Vitkov" <vvitkov@gmail.com> wrote: > > > Remove multipath caching and try again > > > if i remove > CONFIG_IP_ROUTE_MULTIPATH_CACHED > > i will be unable to use : > CONFIG_IP_ROUTE_MULTIPATH_RR > CONFIG_IP_ROUTE_MULTIPATH_RANDOM > CONFIG_IP_ROUTE_MULTIPATH_WRANDOM > CONFIG_IP_ROUTE_MULTIPATH_DRR > > right ?yes correct you will get only random multipath. It works perfectly well> -- > You will always get the greatest recognition for the job you least like. > _______________________________________________ > LARTC mailing list > LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc >-- С уважение, Владимир Витков http://www.netsecad.com http://www.supportbg.com _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc