Date: Tue, 24 Aug 2010 11:18:32 -0700 From: "Li, Qing" <qing.li@bluecoat.com> To: "Ingo Flaschberger" <if@xip.at> Cc: net@freebsd.org Subject: RE: funny ECMP Message-ID: <B583FBF374231F4A89607B4D08578A4307F1FF22@bcs-mail03.internal.cacheflow.com> In-Reply-To: <alpine.LFD.2.00.1008242005160.12708@filebunker.xip.at> References: <alpine.LFD.2.00.1008230154280.29368@filebunker.xip.at> <alpine.LFD.2.00.1008240144350.12708@filebunker.xip.at> <B583FBF374231F4A89607B4D08578A4307F1FC70@bcs-mail03.internal.cacheflow.com> <alpine.LFD.2.00.1008240223240.12708@filebunker.xip.at> <alpine.LFD.2.00.1008242005160.12708@filebunker.xip.at>
index | next in thread | previous in thread | raw e-mail
Hi, The indirect route is colliding with the interface route, both have the same mask. How do you expect this to work ? How would the routing code differentiate between on-link nodes and the those needing to be routed through 10.11.11.1 ? -- Qing > > one of the problems: > sysctl -w net.inet.flowtable.enable=0 > route add 10.13.13.0/24 10.11.11.1 -weight 2 > ifconfig em1 alias 10.13.13.90/24 > > arp-resolve fails: > arpresolve: can't allocate llinfo for 10.13.13.95 > > in sys/netinet/in.c: > in_lltable_lookup calls in_lltable_rtcheck which calls rtalloc1 > rtalloc1 seems to return the first route - and does not check for more. > > diag from in_lltable_rtcheck: > IPv4 address: "10.13.13.95" is not on the network > > checking now how to repair this. > > Kind regards, > Ingo Flaschbergerhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B583FBF374231F4A89607B4D08578A4307F1FF22>