> Thanks Doug, that was exactly right. As soon (had to wait for a dead
> period to test in) as I switched the netmask to 255.255.255.255 things
> were ok! Until I ran into the undestructable route this stops my
> connection from working. I'll plug in the info I got from ifconfig and
> the route info before and after my reboot. I've appended our original
> conversation below since it contains my location table. I've tried it on
> Demand Dial and Manual with the same results.
>
> Here's the route and ifconfig before the reboot notice the SUSPENDED flag
> in the ifconfig output (what does that mean?). This route and ifconfig is
> taken when I am -not- connected.
I don't know what the suspended flag meand.
> 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
The local route ptp53 route is from interface 53. Maybe you have defined
something on S53 or W53 that is causing this to appear like a hardwired
connection defined. The other one looks like a static someone entered
that points at the interface. This looks odd to me. What kind of
portmaster is this?
> 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
>
> Here's what it looks like after a reboot when I dialed in :
>
> 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 ptp8
> 204.134.11.176 28 198.59.115.158 temp NS 1 ptp8
>
> and then when I hang up, that route goes away like it is supposed to. I'm
> not really sure what is causing the route to get stuck in the first place.
> Any help is always appreciated!
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.
Doug Ingraham I have a simple philosophy:
Rapid City, SD Fill what's empty.
USA Empty what's full.
Scratch where it itches.
-- A. R. Longworth
> On Sun, 25 Apr 1999, Doug Ingraham wrote:
>
> > On Sun, 25 Apr 1999, James Hamilton wrote:
> >
> > > Hello, I've got a PM3 that I've set up for dialout. Every time I call my
> > > Netgear ISDN router ether0 quits talking so I have to do an
> > > ifconfig down then ifconfig up to reset it. It seems to only affect
> > > ether0, if I have 2 logins to the PM3 they can still talk locally to
> > > eachother. My location looks like:
> > >
> > > Location: jamesh Type: Manual
> > > Destination: 198.59.115.158 Netmask: 255.255.255.0
> > > Local IP: 198.59.115.110
> > > Protocol: PPP Options: Quiet, VJ-Comp
> > > Group: 0 Max Ports: 2
> > > Idle Timeout: 0 minutes High Mark: 0 bytes
> > > Mtu: 1500 Async Map: 00000000
> > > Username: someuser Password: xxxxxxx
> > >
> > > I'm a bit confused as to why this would occur. This PM3 is running ComOS
> > > 3.8 if that makes any difference. Any advice or comments would be
> > > appreciated!
> >
> > You probably have the wrong netmask. It should probably be
> > 255.255.255.255. The way you have it now it would try to route the whole
> > class C over that interface.
> >
> >
> > Doug Ingraham I have a simple philosophy:
> > Rapid City, SD Fill what's empty.
> > USA Empty what's full.
> > Scratch where it itches.
> > -- A. R. Longworth
> >
>
>
>
>
-
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/>