Re: (PM) Problem location and dial out on demand

portmaster@she.de
Tue, 19 May 1998 18:19:29 +0200 (CEST)

On Tue, 19 May 1998, Stephen Zedalis wrote:

> Date: Tue, 19 May 1998 11:40:26 -0400 (EDT)
> From: Stephen Zedalis <tintype@exis.net>
> To: portmaster@she.de
> Cc: portmaster-users@livingston.com
> Subject: Re: (PM) Problem location and dial out on demand
>
>
> Hmm... This means he is dialed in or you dialed him, right? Since you
> said he can dial-in and you can dial-out manually, the route is there?
> I'm assuming he if dialed in, the Framed-Route took care of the route
> and the netmask takes care of the route when you manually dial
> out to him. The "unknown" interface message should be normal until you
> try to dial out. What does the routing table look like when he hasn't
> dialed in and you haven't dialed him for awhile? His previous route isn't
> there right? Thats where the route to the "unknown" interface should come
> into play. Ie. it looks for a location entry that matches the IP address
> and dials out. As soon as it does, THEN the location table routing entry
> is made. I don't know guys, isn't that how its supposed to work?

the route looks like in my first mailing, when I havent't dial out or in
for a while.

After dialing from the PM3 to the customer the routing table looks like:

Destination Mask Gateway Source Flag Met Interface
----------------- ---- -------------------- ------- ---- --- ---------
0.0.0.0 0 193.98.91.2 local NS 1 ether0
193.141.20.9 32 193.141.20.9 local HL 1 ptp0
193.141.20.8 29 193.141.20.9 temp NS 1 ptp0
194.141.20.8 29 194.141.20.9 local NL 1 ptp32
193.98.91.0 25 193.98.91.54 local NL 1 ether0

after disconnecting the customer (timeout)

Destination Mask Gateway Source Flag Met Interface
----------------- ---- -------------------- ------- ---- --- ---------
0.0.0.0 0 193.98.91.2 local NS 1 ether0
193.141.20.9 32 193.141.20.9 local HL O 16 Unknown
193.141.20.8 29 193.141.20.9 temp NS O 16 Unknown
194.141.20.8 29 194.141.20.9 local NL 1 ptp32
193.98.91.0 25 193.98.91.54 local NL 1 ether0

and then:

Destination Mask Gateway Source Flag Met Interface
----------------- ---- -------------------- ------- ---- --- ---------
0.0.0.0 0 193.98.91.2 local NS 1 ether0
194.141.20.8 29 194.141.20.9 local NL 1 ptp32
193.98.91.0 25 193.98.91.54 local NL 1 ether0

and stays in this state.

Regards,
Ralf

>
> On Tue, 19 May 1998 portmaster@she.de wrote:
>
> >show route
> >Destination Mask Gateway Source Flag Met Interface
> >----------------- ---- -------------------- ------- ---- --- ---------
> >0.0.0.0 0 193.98.91.2 local NS 1 ether0
> >194.141.20.8 29 194.141.20.9 local NL 1 ptp32
> >193.98.91.0 25 193.98.91.54 local NL 1 ether0
> >
> >I think they are created from the location entry, because I did not added
> >it manually.
> >
> >If I add manuelly an routing entry for this subnet, I get the following:
>
> -
> 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/>
>

------------------------------------------------------------------------
Ralf Naegele _/_/_/ _/ _/_/_/
Softwarehaus Engelhardt GmbH _/ _/ _/ Phon: +49 621 5953200
Donnersbergweg 1 _/_/ _/_/_/ _/_/ Fax: +49 621 5953201
D-67059 Ludwigshafen _/ _/ _/ _/ eMail: naegele@she.de
Xlink-PoP LU/HD/KL/DA _/_/_/ _/ _/ _/_/_/ http://www.she.de/
------------------------------------------------------------------------

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