🚀 go-pugleaf

On Mon, 11 May 1998, Stuart Pierce wrote:

> 
> What do you make of this ?
> 
>  interface "wilhelmsen-ppp" down
> Mon May 11 15:55:50 1998 - wilhelmsen-ppp PPP/IPCP Pool add route to
> peer (207.40.12.111)
> Mon May 11 15:55:51 1998 - interface "wilhelmsen-ppp" up
> Mon May 11 15:55:51 1998 - interface "wilhelmsen-ppp" up
> Mon May 11 15:55:51 1998 - interface "wilhelmsen-ppp" down
> Mon May 11 15:55:51 1998 - interface "wilhelmsen-ppp" down
> Mon May 11 15:55:51 1998 - wilhelmsen-ppp PPP/IPCP Pool add route to
> peer (207.40.12.112)
> Mon May 11 15:55:51 1998 - interface "wilhelmsen-ppp" up
> Mon May 11 15:55:51 1998 - interface "wilhelmsen-ppp" up
> Mon May 11 15:55:51 1998 - interface "wilhelmsen-ppp" down
> Mon May 11 15:55:51 1998 - interface "wilhelmsen-ppp" down

[etc]

The interface is going up and down (IPCP is opening and closing and
opening again, etc) and since the NetBlazer is assigning an IP address to
the remote end it is pulling a different one from the pool each time.

The real problem is finding out what is causing IPCP to keep
renegotiating, and there is not enough information here to tell.  A "ppp
trace wilhelmsen-ppp ipcp bad fsm" -- or even a "ppp trace wilhelmsen-ppp
all" -- command might give enough information. Also, if you can perform a
similar trace at the remote end of the connection you can see what it
thinks is going on.  The NetBlazer should not be initiating all these
renegotiations so the cause may lie in how the remote end is responding to
what it sees.

Thanks,
Mike
-- 
Mike Thornburg         |  I do not speak for frigate networks;
mthorn@frigate.com     |  I'm just a guest here now.