Subject: bin/4387: ipmon fails to monitor like it should
To: None <gnats-bugs@gnats.netbsd.org>
From: Michael Graff <explorer@flame.org>
List: netbsd-bugs
Date: 10/29/1997 13:06:44
>Number:         4387
>Category:       bin
>Synopsis:       ipmon fails to monitor like it should
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Oct 29 10:20:01 1997
>Last-Modified:
>Originator:     Michael Graff
>Organization:
flame.org:  yes, we do know everything
>Release:        28-Oct-1997
>Environment:
	
System: NetBSD kechara.flame.org 1.3_ALPHA NetBSD 1.3_ALPHA (KECHARA) #0: Tue Oct 28 13:40:55 EST 1997 explorer@kechara.flame.org:/u1/OS/NetBSD/src/sys/arch/i386/compile/KECHARA i386


>Description:
ipmon will not "tail" the connection like it should.  It will dump the
current log messages, then hang.  Killing and restarting it will cause the
latter messages to once again appear.
>How-To-Repeat:
# ipmon
29/10/1997 13:01:55.846741 de0 @6 p 198.216.104.45,1925 -> 192.80.44.210,9000 PR tcp len 20 44 -S
...
29/10/1997 13:02:03.653295 de0 @1 p 192.80.44.209,4462 -> 204.191.136.8,113 PR tcp len 20 60 -S
<HANG>
^C

# ipmon 
29/10/1997 13:02:13.632412 de0 @1 p 192.80.44.210,4461 -> 198.216.104.45,113 PR tcp len 20 60 -S
...
<HANG>
^C

# ipmon
29/10/1997 13:02:34.399120 lo0 @8 p 192.80.44.209,4463 -> 192.80.44.209,6002 PR tcp len 20 60 -S
...
29/10/1997 13:04:19.040082 de0 @2 p 192.80.44.209,25 -> 132.249.66.211,1149 PR tcp len 20 44 -AS
<HANG>

>Fix:
I dunno, I've not looked at it hard enough yet.
>Audit-Trail:
>Unformatted: