After a boot, routing for this location shows:
trd-pm2> show route 172.29.200.1
Destination Mask Gateway Source Flag Met Interface
----------------- ---- -------------------- ------- ---- --- ---------
172.29.200.0 24 172.29.200.1 local NL 1 ptp22
trd-pm2> show route 172.29.200.0
Destination Mask Gateway Source Flag Met Interface
----------------- ---- -------------------- ------- ---- --- ---------
172.29.200.0 24 172.29.200.1 local NL 1 ptp22
*After* the first dial, it seems, the routes are changed. From my PC, I
now get a "destination unreachable" from the PM when tracerouting to
this location. The routes show:
trd-pm2> show route 172.29.200.1
Destination Mask Gateway Source Flag Met Interface
----------------- ---- -------------------- ------- ---- --- ---------
172.29.200.1 32 172.29.200.1 local HL 1 ptp22
trd-pm2> show route 172.29.200.0
Destination Mask Gateway Source Flag Met Interface
----------------- ---- -------------------- ------- ---- --- ---------
trd-pm2>
How come this is changed to a host route?
I have no filters on ether0. Also, ifconfig shows the following:
ptp22:
flags=765<IP_UP,IPX_DOWN,POINT_TO_POINT,PRIVATE,IFILTER,OFILTER,SUSPENDE
D
>
dest 172.29.200.1 netmask ffffffff mtu 1500
ptp23: flags=165<IP_UP,IPX_DOWN,POINT_TO_POINT,PRIVATE,SUSPENDED>
dest 172.29.220.253 netmask ffffff00 mtu 1500
Notice the IFILTER,OFILTER in ptp22 (which doesn't work). Why are they
there? There are NO filters on this location, have even done set <loc>
ifilter, set <loc> ofilter and save all to make sure. How can I remove
them?
Ideas?
(Incidentally, there are Cisco 761s in the other end of both these
locations. They are running different versions. I believe the one which
works is running 4.2(1) and the one that doesn't is running 4.1(1) or
something. *Should* be no routes propagated, but we'll still try to get
the one upgraded and re-check the config.)
-tsb
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>