From owner-freebsd-hackers Sun Apr 21 13:37:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA05596 for hackers-outgoing; Sun, 21 Apr 1996 13:37:55 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA05493 Sun, 21 Apr 1996 13:37:40 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA26388; Sun, 21 Apr 1996 22:37:37 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id WAA00302; Sun, 21 Apr 1996 22:37:33 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id VAA15294; Sun, 21 Apr 1996 21:43:42 +0200 (MET DST) From: J Wunsch Message-Id: <199604211943.VAA15294@uriah.heep.sax.de> Subject: Re: ipcp loop To: fyeung@fyeung5.netific.com (francis yeung) Date: Sun, 21 Apr 1996 21:43:41 +0200 (MET DST) Cc: questions@freebsd.org, hackers@freebsd.org, fyeung@fyeung5.netific.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604192314.XAA10011@fyeung5.netific.com> from "francis yeung" at Apr 19, 96 11:14:37 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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. ;-)