-----------------
Linux with radius
205.152.26.2
-----------------
---------------- | -------------
Bell south router------ hub----- PM/30
205.152.26.1 | 205.152.26.30
T1 to Internet | -------------
---------------- |
--------------------
Cisco 2501
205.152.26.7
secondary 192.168.1.1
---------------------
|
frame relay
|
----------- ----------------
Cisco 2501----hub---Portmaster pm/10
192.168.2.1 192.168.2.10
----------- ----------------
Ok now here is a traceroute from the linux box to the PM
traceroute to 192.168.2.10 (192.168.2.10), 30 hops max, 40 byte packets
1 mi-fr-1.rt.agetech.net (205.152.26.7) 2.753 ms 2.437 ms 2.925 ms
2 br-fr-1.rt.agetech.net (192.168.2.1) 12.234 ms 8.499 ms 8.582 ms
3 192.168.2.10 (192.168.2.10) 9.39 ms 7.392 ms 9.437 ms
ns1:~#
Seems to be fine right, well for some reason after a week or so the
Linux box looses the route to
the frame realy and instead goes to the bell south router at
205.152.26.1. Now I notice ICMP redirects from the Cisco at the
205.152.26.7 so I decided to add these routes in the Radius server.
Kernel routing table
Destination Gateway Genmask Flags MSS Window Use
Iface
localnet * 255.255.255.0 U 1500 0 21346
eth0
192.168.0.0 mi-fr-1.rt.aget 255.255.0.0 UG 1500 0 135
eth0
loopback * 255.0.0.0 U 3584 0 36
lo
default router.agetech. * UG 1500 0 110091
eth0
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?