From owner-freebsd-current Fri Nov 14 08:02:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA08988 for current-outgoing; Fri, 14 Nov 1997 08:02:58 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp.algonet.se (tomei.algonet.se [194.213.74.114]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA08978 for ; Fri, 14 Nov 1997 08:02:54 -0800 (PST) (envelope-from johang@mail.algonet.se) Message-Id: <199711141602.IAA08978@hub.freebsd.org> Received: (qmail 3941 invoked from network); 14 Nov 1997 17:02:47 +0100 Received: from du156-3.ppp.algonet.se (HELO pegasys) (195.100.3.156) by tomei.algonet.se with SMTP; 14 Nov 1997 17:02:47 +0100 Comments: Authenticated sender is From: "Johan Granlund" To: current@FreeBSD.ORG Date: Fri, 14 Nov 1997 17:02:40 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: ppp and ascend router problems CC: Brian Somers Priority: normal In-reply-to: <199711132339.XAA21225@awfulhak.demon.co.uk> References: Your message of "Thu, 13 Nov 1997 19:08:04 +0100." <199711131806.NAA02823@mailman.iuinc.com> X-mailer: Pegasus Mail for Win32 (v2.54) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [.....] > > The peer is behaving differently. If this is the same peer, I'd be > surprised. The funny thing here is that we manage to squeeze two > CONFIG REQs out before the peer sends anything. The peer doesn't REQ > for four seconds. The ``uninteresting'' thing is that your last posting > detailed exactly the same behaviour (3 seconds that time), *except* that > the second CONFIG REQ from the peer asked for the [13] again and again > the first time 'round. This time, it behaves correctly and removes the > [13] from the REQ. This is gettin funnier all the time. Copied the ppp program from the -stable machine and tried it on the -current machine. The ppp-stable behaved exactly the same as ppp-current. Either it is something fundamentally wrong in the kernel/tun driver (i don't believe it) or i get connected to two different ascend routers. The -current machine dials from a normal analog phoneline. The -stable is connected to a company exchange that is connected with a primary ISDN trunk. I have sent a partial trace and some questions to my ISP. More to come and thanks for the help /Johan > > I'd examine this with whoever controls (and hopefully understands) > the peer. Basically, if we send a REJ, the peer *must not* REQ the > things that we REJ. We are entitled to drop the connection > immediately if this happens because the peer is violating the ppp > protocol. > > Perhaps you ought to get these guys to update to the next (apparently > daily) version of software :-I > > > ___________________________________________________________ > > > > Internet: Johang@Algonet.se > > > > I don't even speak for myself > > -- > Brian , , > > Don't _EVER_ lose your sense of humour.... > > > > ___________________________________________________________ Internet: Johang@Algonet.se I don't even speak for myself