From owner-freebsd-bugs Wed Sep 1 23:59:41 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id DF05A14F5C for ; Wed, 1 Sep 1999 23:59:37 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (root@localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id HAA65724; Thu, 2 Sep 1999 07:59:22 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA60637; Thu, 2 Sep 1999 08:03:19 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199909020703.IAA60637@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Kerry Morse Cc: "'Brian Somers'" , freebsd-bugs@FreeBSD.org Subject: Re: bin/13506: Problem with ppp octet counter rolling into negati ves. In-reply-to: Your message of "Thu, 02 Sep 1999 08:43:37 +1000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Sep 1999 08:03:19 +0100 From: Brian Somers Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org kerry.morse@metrotas.com.au said: > Ok... Basically then link had been up for approximately 8 days, in > which time had been working fine, reestablishing connections > correctly, only this time when the counter had rolled into the > negative, it ceased to work at all, the phone line stayed connected. > Once ppp was terminated and restarted it started working correctly > and has done since. I just found it kinda funny that it stopped > working about the time it went negative and thought you might be > interested to know. I'll look at enabling LCP, chat and IPCP logging > tonight; filters none enabled. Which counter are we talking about ? The throughput counters are unsigned long longs in the latest sources.... If this is what wrapped, I find it surprising that that would cause any problems. As well as enabling the above logging (I wouldn't bother with the tcp/ip logging if the connection's going to be up 8 days and there are no filters), it may be worth enabling a diagnostic socket (set server) and when it jams, make a connection and do a ``show mem''. This'll show if there are any outstanding packets. A ``show links'' would be interesting too and maybe a ``show physical'' (or ``show modem'' if you're running an older version). -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message