Date: Wed, 2 May 2001 08:44:19 -0500 From: Eric_Stanfield@kenokozie.com To: freebsd-isp@freebsd.org Subject: server getting bogus route info from ??? Message-ID: <OF1A7FF88D.F6D93BE4-ON86256A40.004AA3FE@kka.com>
next in thread | raw e-mail | index | archive | help
I have a machine set up to run some apps like mrtg and netsaint. This machine monitors a corporate wan with 4 offices in the US. washington d.c. 10.1.0.0/16 chicago 10.2.0.0/16 (netsaint is here) boston 10.3.0.0/16 portland 10.4.0.0/16 Netsaint is configured to page me if it can no longer connect to the wan router on one of these networks. Each lan has it's own internet connection and a separate router that handles internet traffic. The problem that is coming up occasionally is that netsaint pages me saying it can no longer see the boston wan router at 10.3.1.2. Yet, when I telnet into the netsaint box and do a traceroute the traffic is trying to exit the chicago internet router instead of going through the chicago wan router and into the frame. If I telnet into the Chicago wan router, I can ping the boston wan router successfuly so the Chicago wan router does have the proper route info. I have tried to tell the netsaint box not to accept icmp redirects thinking that maybe the link to boston really is going down for a minute and the chicago wan router is sending redirects for that route to the internet router. I actually thought this might have solved the problem, but this morning after a few weeks of peace and quiet the same situation has cropped up again. Route table on the netsaint box is not showing a new route to boston, it always looks like this (which is correct): Destination Gateway Genmask Flags MSS Window irtt Iface 10.2.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 10.3.0.0 10.2.1.2 255.255.0.0 UG 0 0 0 eth0 10.1.0.0 10.2.1.2 255.255.0.0 UG 0 0 0 eth0 10.4.0.0 10.2.1.2 255.255.0.0 UG 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 10.2.1.2 0.0.0.0 UG 0 0 0 eth0 0.0.0.0 10.2.1.2 0.0.0.0 UG 0 0 0 eth0 Actual ip's of the wan routers are: 10.1.1.2 = washington 10.2.1.2 = chicago 10.3.1.2 = boston 10.4.1.2 = portland This ONLY happens with the boston route. The netsaint box isn't set up to receive rip info (and there shouldn't be any being sent into the lan anyways). I'm at a total loss. Rebooting the machine is the only thing that clears this up. Anyone have an idea? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Eric Stanfield, K2Access Keno Kozie Associates 222 N LaSalle #1500 Chicago, IL 60606 (312) 332-3000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?OF1A7FF88D.F6D93BE4-ON86256A40.004AA3FE>