Date: Sun, 21 Apr 1996 21:43:41 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: fyeung@fyeung5.netific.com (francis yeung) Cc: questions@freebsd.org, hackers@freebsd.org, fyeung@fyeung5.netific.com Subject: Re: ipcp loop Message-ID: <199604211943.VAA15294@uriah.heep.sax.de> In-Reply-To: <199604192314.XAA10011@fyeung5.netific.com> from "francis yeung" at Apr 19, 96 11:14:37 pm
next in thread | previous in thread | raw e-mail | index | archive | help
As francis yeung wrote: > 07-11 07:14:34 [154] IPCP: state change Initial --> Closed > 07-11 07:14:34 [154] IPCP Up event!! > 07-11 07:14:34 [154] IPCP: SendConfigReq > 07-11 07:14:34 [154] IPADDR [6] 192.0.0.1 > 07-11 07:14:34 [154] COMPPROTO [6] 002d0f00 > 07-11 07:14:34 [154] IPCP: state change Closed --> Req-Sent ... > 07-11 07:14:37 [154] IPCP: Received Configure Request (3) state = Req-Sent (6) > 07-11 07:14:37 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:37 [154] IPCP: SendConfigAck(Req-Sent) > 07-11 07:14:37 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:37 [154] IPCP: state change Req-Sent --> Ack-Sent > 07-11 07:14:40 [154] IPCP: Received Configure Request (4) state = Ack-Sent (8) > 07-11 07:14:40 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:40 [154] IPCP: SendConfigAck(Ack-Sent) > 07-11 07:14:40 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:43 [154] IPCP: Received Configure Request (5) state = Ack-Sent (8) > 07-11 07:14:43 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:43 [154] IPCP: SendConfigAck(Ack-Sent) > 07-11 07:14:43 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:46 [154] IPCP: Received Configure Request (6) state = Ack-Sent (8) > 07-11 07:14:46 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:46 [154] IPCP: SendConfigAck(Ack-Sent) > 07-11 07:14:46 [154] IPADDR[6] 168.95.127.222 > 07-11 07:14:49 [154] IPCP: Received Configure Request (7) state = Ack-Sent (8) > 07-11 07:14:49 [154] IPADDR[6] 168.95.127.222 > > ... > > It seems to me that there was an IPCP collision and Xylogics never ack'd > iijppp's SendConfigAck(Ack-sent). > > Is this a ijjppp problem or a Xylogics problem ? This looks like a Xylogics problem, but you cannot be sure until you've also seen the logs from the remote peer. The above looks like iijppp is flooded with config request that are properly acknowledged. The requested 192.0.0.1 address is arguably bogus (and we've been there with the author of iijppp, if i remember well), however the Xylogics should simply NAK it and come up with its own suggestion. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604211943.VAA15294>