Nick Gustas wrote: > Oct 4 19:03:09 xxxxxxx ppp[55]: tun0: Phase: bundle: Authenticate > Oct 4 19:03:09 xxxxxxx ppp[55]: tun0: Phase: deflink: his = PAP, mine = none > Oct 4 19:03:09 xxxxxxx ppp[55]: tun0: Phase: Pap Output: [EMAIL PROTECTED] > ******** > Oct 4 19:03:09 xxxxxxx ppp[55]: tun0: LCP: deflink: RecvCodeRej(127) state = > Opened > Oct 4 19:03:11 xxxxxxx ppp[55]: tun0: Phase: Pap Input: SUCCESS () > > The real question is, is there's a way to work around your provider's > brokenness without > killing the ppp process?
Hi Nick, I cranked up the debug logging, and compared my ppp login attempts with your logfile. I get multiple Oct 6 18:29:43 coyote ppp[67945]: tun0: IPCP: deflink: RecvConfigReq(12) state = Initial Oct 6 18:29:43 coyote ppp[67945]: tun0: IPCP: IPADDR[6] 213.191.89.20 Oct 6 18:29:43 coyote ppp[67945]: tun0: IPCP: deflink: Oops, RCR in Initial. Oct 6 18:29:46 coyote ppp[67945]: tun0: IPCP: deflink: RecvConfigReq(13) state = Initial Oct 6 18:29:46 coyote ppp[67945]: tun0: IPCP: IPADDR[6] 213.191.89.20 Oct 6 18:29:46 coyote ppp[67945]: tun0: IPCP: deflink: Oops, RCR in Initial. Using "Google Search" then led me to the follow posts [1], that describe the problem in more detail. 'disable ipv6cp' should do the trick, I'll check this ASAP. Thanks for your pointer! [1] http://www.freebsd.de/archive/de-bsd-questions/de-bsd-questions.200506/0029.html http://tech.barwick.de/openbsd/deflink-oops-rcr-in-initial.html Ulrich Spoerlein -- A: Yes. >Q: Are you sure? > >A: Because it reverses the logical flow of conversation. > >>Q: Why is top posting frowned upon? _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
