TCP/IP Testing help, Round 2

[der Mouse]

> Found it!  Testing is open again - hammer away at will!

Cool!  I left you with a deliberately half-open socket, for your
testing pleasure.  (I tried to leave you with another one, but it went
away - and the rest of the connections didn't, so I don't think it was
you resetting things.)  It's the one from 216.46.1.51:64971.  (I
created it by connecting and then hard-resetting the machine.)

> Telnet users:

> My understanding of telnet is that it is a protocol, not just raw
> characters.

You are correct.  See RFC 854. :-)

> So when you hit Ctrl-C under a typical Telnet client in Unix, you are
> sending the equivalent of a 'process' interrupt.

Most likely an Interrupt Process (0xff 0xf4) sequence, quite possibly
an Abort Output (0xff 0xf5) and/or a Synch (0xff 0xf2 with the TCP
urgent pointer pointing just after the 0xf2) as well.

> I see lots of funny characters on my side, but they'll get consumed
> and life goes on.  I suspect that telnet is not so tolerant though,
> and is expecting a proper response back from the telnet server.

I'm inclined to doubt it.  There is no defined response that a telnet
client can reasonbly expect to IP, AO, or Synch.

I'll snoop traffic and try a ^C to see what's really going on - at the
wire level, at least.

> Anybody notice the BIOS date and machine ID?  That's generated at
> runtime, not a static string. :-)

I noticed it, but had no way to tell whether it were static or not. :)

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse at rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B