Whoa, this was weird ...

Telnetted from a SunOS 4.1.4 box to a NetBSD/i386 1.1 P120 PC.  I did a grep
on something in the gcc tree, and it generated oodles of output.  I tried
to ^C it ... I managed to get the output to stop.  But then the terminal
didn't come back; the other end (PC end) didn't get flushed or something.
I tried ^C, ^\, etc.  Tried resetting my local xterm to see if the pty was
wedged.  Nothing.  Finally, I quit out of the telnet to close the connection.

This was immediately followed by a 30-45 second+ rash of flurried packets.
The local side kept sending FINs to the NetBSD side, but the NetBSD side kept
ignoring them, and the telnetd kept firing back at it.  A snippet follows:

02:36:39.046362 128.149.24.254.2182 > 137.78.70.110.23: F 0:0(0) ack 4294967295 win 0 (ttl 60, id 26301)
02:36:39.104771 137.78.70.110.23 > 128.149.24.254.2182: . ack 1 win 16384 urg 10917 [tos 0x10] (ttl 60, id 2215)
02:36:39.105184 137.78.70.110.23 > 128.149.24.254.2182: . ack 1 win 16384 urg 10917 [tos 0x10] (ttl 60, id 2216)
02:36:39.105781 128.149.24.254.2182 > 137.78.70.110.23: F 0:0(0) ack 4294967295 win 0 (ttl 60, id 26302)
02:36:39.425771 137.78.70.110.23 > 128.149.24.254.2182: . ack 1 win 16384 urg 10917 [tos 0x10] (ttl 60, id 2231)
02:36:39.426540 128.149.24.254.2182 > 137.78.70.110.23: F 0:0(0) ack 4294967295 win 0 (ttl 60, id 26318)
02:36:39.435327 137.78.70.110.23 > 128.149.24.254.2182: . ack 1 win 16384 urg 10917 [tos 0x10] (ttl 60, id 2232)
02:36:39.435848 137.78.70.110.23 > 128.149.24.254.2182: . ack 1 win 16384 urg 10917 [tos 0x10] (ttl 60, id 2233)
02:36:39.437795 128.149.24.254.2182 > 137.78.70.110.23: F 0:0(0) ack 4294967295 win 0 (ttl 60, id 26319)
02:36:39.438496 128.149.24.254.2182 > 137.78.70.110.23: F 0:0(0) ack 4294967295 win 0 (ttl 60, id 26320)
02:36:39.495586 137.78.70.110.23 > 128.149.24.254.2182: . ack 1 win 16384 urg 10917 [tos 0x10] (ttl 60, id 2234)
02:36:39.496005 137.78.70.110.23 > 128.149.24.254.2182: . ack 1 win 16384 urg 10917 [tos 0x10] (ttl 60, id 2235)

[ ... Oodles more ... ]

02:36:45.076360 128.149.24.254.2182 > 137.78.70.110.23: F 0:0(0) ack 4294967295 win 0 (ttl 60, id 26598)
02:36:45.076931 128.149.24.254.2182 > 137.78.70.110.23: F 0:0(0) ack 4294967295 win 0 (ttl 60, id 26599)
02:36:45.091820 137.78.70.110.23 > 128.149.24.254.2182: . ack 1 win 16384 urg 10917 [tos 0x10] (ttl 60, id 2513)
02:36:45.092254 137.78.70.110.23 > 128.149.24.254.2182: . ack 1 win 16384 urg 10917 [tos 0x10] (ttl 60, id 2514)
02:36:45.093017 128.149.24.254.2182 > 137.78.70.110.23: F 0:0(0) ack 4294967295 win 0 (ttl 60, id 26600)
^C02:36:45.166006 137.78.70.110.23 > 128.149.24.254.2182: . ack 1 win 16384 urg 10917 [tos 0x10] (ttl 60, id 2517)

835 packets received by filter
292 packets dropped by kernel

Somehow this doesn't seem right.  How could the NetBSD telnetd keep ignoring
all the FINs like this?

(Shortly thereafter, my PPP link went down.  Maybe it got tired out from all
 those packet bursts  (-: )

	- Greg