Routing problems.
Zach Tippit (sterno@verinet.com)
Thu, 28 Aug 1997 09:53:10 -0600 (MDT)
We have a few portmasters in our dialin pool here, and two class C
networks. 204.144.246 is our primary according to the cisco, and
207.174.14 is the secondary. The first three PM2E machines are on
204.144.246 and assign addresses from that pool. The last one is on
207.174.14 and assigns from that pool. However, we have some users who
get a static IP on the 204.144.246 network. When they hit that last
portmaster, they can ping it(207.174.14.9) and it can ping them, but the
route does not advertise across the network. I was told by a livingston
tech that this is because Cisco routers are not capable of dynamically
routing through the secondary address(207). He told me to put a static
route on the cisco with a high administrative distance. So I put one on
that routes 204.144.246.8 through 207.174.14.9(that last pm2e). If a rip
broadcast comes through that reports differently, it takes precedence over
the static route due to the high administrative distance. With this route
in place, the 204.144.246.8 user can dial into 207.174.14.9, ping the
router at 207.174.14.1 and at 204.144.246.1 but not any further? Any
ideas, anyone? anyone?
Zach
Verinet Communications