> Brian Somers wrote:
> > I've had reports of this in the past. The other end is sending a
> > ``code 5'' packet - something that doesn't appear in the spec :(
> > ppp(8) just ignores these (emitting a warning), they shouldn't be
> > causing any problems themselves (even if CBCP is actually being used).
> > Try enabling IPCP logging. You may be having a problem at that
> > level, or alternatively, perhaps the peer thinks you've already got a
> > connection and is (rudely) dropping the connection because of that.
> Attached please find relevant log. I could add that now the problem became even
> more frequent, so I would appreciate any help.
> Thank you!
> Phase: Pap Output: sobomax1 ********
> Phase: Pap Input: SUCCESS ()
So authentication is ok.
> IPCP: deflink: LayerUp.
> IPCP: myaddr 22.214.171.124 hisaddr = 126.96.36.199
The IP layer is up.
> IPCP: deflink: RecvTerminateReq(3) state = Opened
> IPCP: deflink: LayerDown: 188.8.131.52
And the peer closes the connection.
To be honest, I have no idea what's going on here. It doesn't even
look as if you sent any data. I think you may have to ask your ISP
why they're closing the connection :/
Brian <[EMAIL PROTECTED]> <brian@[uk.]FreeBSD.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message