A loopback route is spontaneously added with hidden arp patch?

From: Nir Soffer (nirs@exanet.com)
Date: Tue Dec 31 2002 - 05:08:27 EST


Hi!

I'm running 2.4.18-14 in a heavy network environment. The machine itself
is a dual CPU P3 (though I've seen the same thing on other platforms
with different kernels). The kernel itself is patched with the hidden
arp patches and is running a proprietary IP load balancing module (from
www.ipmetrics.com ).

I've seen several times where the routing table has become corrupted in
such a way so all connections to 10.0.0.0 go to the loopback.

The output of ip route ls table all is:
local 10.0.18.230 dev lo table local proto kernel scope host src
10.0.18.230
broadcast 127.255.255.255 dev lo table local proto kernel scope link
src 127.0.0.1
local 10.48.0.3 dev eth1 table local proto kernel scope host src
10.48.0.3
local 10.0.18.210 dev lo table local proto kernel scope host src
10.0.18.210
local 10.16.0.3 dev eth0 table local proto kernel scope host src
10.16.0.3
local 10.0.18.220 dev lo table local proto kernel scope host src
10.0.18.220
local 10.0.18.12 dev eth3 table local proto kernel scope host src
10.0.18.12
broadcast 127.0.0.0 dev lo table local proto kernel scope link src
127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src
127.0.0.1
local 10.0.0.0/8 dev lo table local proto kernel scope host src
10.0.18.210
^^^^^^^^^^^
local 127.0.0.0/8 dev lo table local proto kernel scope host src
127.0.0.1

As you can see, the second to last line is a route table entry that
routes everything to 10.0.0.0/8 to the loopback addr.

10.0.18.210 is an IP alias configured on the loopback interface, for use
with the hidden arp patch.

Has anyone ever encountered such a situtation, or does anyone have any
hints how we can solve this?

Thanks!
Nir.

--
Nir Soffer -=- Software Engineer, Exanet Inc. -=-
"The poor little kittens; They lost their mittens;
 And now you all must die. Mew, Mew, Mew, Mew, 
 And now you all must die." www.sluggy.com, 24/10/02
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Tue Dec 31 2002 - 22:00:19 EST