Re: Routes
Stephen Zedalis (tintype@exis.net)
Mon, 30 Dec 1996 09:25:00 -0500 (EST)
Any reason, why you did not number the frame-relay interface? Rather than
secondary IP'ng the ether interface? My guess is a fluctuating interface
and RIP and you are not redistributing static routes via RIP, nor are you
listening to routing protocols with the linux box? So, if the static route
gets lost long enough (ie. if the Linux box ether interface goes down for
any reason), it gets dropped. And the default router picks up
the packets headed for the 192.168.x.x interface. When the route comes
back up and the Cisco's talk RIP to each other, the kernel redirects
start. But the linux box has dropped the route, doesn't listen to RIP,
and has no clue but to send the packets to the default router. You could
look for the static route in your route tables and see if it is still
there when you get redirects. If not, write a script that checks to see
if the route is down and re-adds it if it is. Use cron to run it
periodically.
On Mon, 30 Dec 1996 alexm@agetech.net wrote:
> internal networking goes to 205.152.26.7 which is dual homing and the
> rest goes to the Bell south router. The ICMP redirect messages in the
> syslog files went away but again after a few weeks the 192.168.2.?
> network went straight to the bellsouth router. Anyone have any ideas
> why?