From owner-freebsd-bugs Thu Sep 2 0: 7: 2 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from Luey.metrotas.com.au (Luey.metrotas.com.au [147.109.164.1]) by hub.freebsd.org (Postfix) with ESMTP id DD2D815512 for ; Thu, 2 Sep 1999 00:06:51 -0700 (PDT) (envelope-from kerry.morse@metrotas.com.au) Received: from blitzen.metrotas.comau (Blitzen.metrotas.com.au [147.109.164.244]) by Luey.metrotas.com.au (8.9.0/8.9.1) with ESMTP id RAA10638; Thu, 2 Sep 1999 17:05:59 +1000 (EST) Received: by Blitzen.metrotas.com.au with Internet Mail Service (5.0.1460.8) id ; Thu, 2 Sep 1999 17:05:59 +1000 Message-ID: From: Kerry Morse To: "'Brian Somers'" , Kerry Morse Cc: freebsd-bugs@FreeBSD.org Subject: RE: bin/13506: Problem with ppp octet counter rolling into negati ves. Date: Thu, 2 Sep 1999 17:05:58 +1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1460.8) Content-Type: multipart/alternative; boundary="---- =_NextPart_001_01BEF511.9BDB6590" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------ =_NextPart_001_01BEF511.9BDB6590 Content-Type: text/plain 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). Was kinda wondering what the tcp/ip logging was going to be like. Can't even prove that it will fail again. The counter is the output octets (bytes??) counter, the version is the standard one that came with 3.2-RELEASE, I'll enable the diagnostic socket and checking next time.. That's what I get for running a news server on my home machine . ------ =_NextPart_001_01BEF511.9BDB6590 Content-Type: text/html RE: bin/13506: Problem with ppp octet counter rolling into negati ves.

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).

Was kinda wondering what the tcp/ip logging was going to be like.
Can't even prove that it will fail again.
The counter is the output octets (bytes??) counter, the version is
the standard one that came with 3.2-RELEASE, I'll enable the
diagnostic socket and checking next time.. That's what I get for
running a news server on my home machine <GRIN>.

------ =_NextPart_001_01BEF511.9BDB6590-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message