(PM) Re: indestructable route & more location stuff

jamesh@swcp.com
Mon, 3 May 1999 12:08:58 -0600 (MDT)

Here's the short version. I have an account at this ISP, My Netgear
router dials in from home when I'm there causing the connection to go up.
I also wanted a connection to be available from remotly so I created the
location to call my netgear. I am assigned the static address of
198.59.115.158. The other portion of this route that is showing is my
subnet. This is on a PM3 with ComOS 3.8. I basically want the pm3 to
call my netgear give me the address of 198.59.115.158 and then destruct
the route when it hangs up the connection. It calls once makes a route
then the route never goes away. The 204.134.11.176/28 is announced by our
perimater router. The 198.59.115.158 is something set up in RADIUS.

PM3 with the My netgear's eth0 is routed on
198.59.115.110--198.59.115.158/32-------204.134.11.176/28
location table WAN Address my netgear.

We had a similar problem with another location we set up where the route
would be created then never destroyed. I've tried to manually delete it
and I can't kill it without a reboot. Which means I can't use my dialin
with our rebooting the portmaster. If I log in the PM3 won't assign me
the 198.59.115.158 address because it thinks it is already in use. But
It's not. Pretty perplexing.

> I am confused about what you are doing. If you are dialing into the pm
> from home why do you have a location table? Location tables are used for
> the PM to dial out. If you specify an IP address in a location table the
> PM will announce it using the routing protocols you have configured and if
> on demand will make the connection at the time there is some traffic for
> that destination. You should have a location table in only one PM for a
> given location or all of them will be announcing that they have a route to
> that IP address. And I don't think that will work very well. If you are
> doing what I think you are doing you want to delete the location table
> completely and either configure your radius user table properly or put in
> a user entry in the pm.

> dpm4> show route 198.59.115.158
> Destination Mask Gateway Source Flag Met Interface
> ----------------- ---- -------------------- ------- ---- --- ---------
> 198.59.115.158 32 198.59.115.158 local HL 1 ptp53
> 204.134.11.176 28 198.59.115.158 temp NS 1 ptp53

> dpm4> ifconfig
> ether0: flags=16<IP_UP,IPX_DOWN,BROADCAST>
> inet 198.59.115.110 netmask ffffff00 broadcast 198.59.115.0 mtu
> 1500
> ptp57: flags=125<IP_UP,IPX_DOWN,POINT_TO_POINT,PRIVATE>
> dest 198.59.115.174 netmask ffffffff mtu 1500
> ptp61: flags=125<IP_UP,IPX_DOWN,POINT_TO_POINT,PRIVATE>
> dest 198.59.115.143 netmask ffffffff mtu 1500
> ptp53:
flags=1ed<IP_UP,IPX_DOWN,POINT_TO_POINT,PRIVATE,COMPRESS,SUSPENDED>
> dest 198.59.115.158 netmask ffffffff mtu 1500
> ptp50: flags=1ad<IP_UP,IPX_DOWN,POINT_TO_POINT,PRIVATE,COMPRESS>
> dest 198.59.115.222 netmask ffffffff mtu 1500
> ptp55: flags=1ad<IP_UP,IPX_DOWN,POINT_TO_POINT,PRIVATE,COMPRESS>
> dest 204.134.10.177 netmask ffffffff mtu 1500
> ptp5: flags=1ad<IP_UP,IPX_DOWN,POINT_TO_POINT,PRIVATE,COMPRESS>
> dest 204.134.5.204 netmask ffffffff mtu 1500
> ptp49: flags=125<IP_UP,IPX_DOWN,POINT_TO_POINT,PRIVATE>
> dest 204.134.5.196 netmask ffffffff mtu 1500
> ptp52: flags=125<IP_UP,IPX_DOWN,POINT_TO_POINT,PRIVATE>
> dest 204.134.5.229 netmask ffffffff mtu 1500
> ptp54:
flags=1ed<IP_UP,IPX_DOWN,POINT_TO_POINT,PRIVATE,COMPRESS,SUSPENDED>
> dest 192.168.1.1 netmask ffffffff mtu 1500

-
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/>