PCjr Telnet Server Test

[Michael B. Brutman]

Jules Richardson wrote:
> Re. testing, is there any way to write something that runs on remote 
> systems and just hammers the network stack / telnet interface on the 
> PCjr, or does nothing like that exist already? It seems like so many 
> TCP/IP stacks have been written for various machines over the years that 
> it surprises me nobody's come up with a solution for automating some of 
> the testing.
> 
> cheers
> 
> Jules
> 
> 

Testing plug: the PCjr is still running at 97.86.233.68



Testing exercises what the test writer expects to break.  I've tested 
quite extensively already, but every once in a while I need to get 
outside help to try to break things in new and exciting ways.

Between the cctalk mailing list and the vintage-computer.com web forum, 
I've got quite a bit of variety.

And just like a good testing effort should, I was caught by something I 
didn't expect and and plan for ..  trouble with retransmits and sequence 
numbers while negotiating a connection.  I've paid so much attention to 
the common case (established connections) that it seems to work pretty 
well.  The three way handshake code gets executed far less and I have 
less ability to break it (being on a local network), so it makes sense 
that the first serious bug was found there.

Btw, everybody must have testing fatigue ..  We're only up to about 50 
connections since I fixed the suspected bug and restarted things.  Feel 
free to telnet back in again with whatever you've got handy ...

The address again is: 97.86.233.68

I'm seeing lots of what look like Windows clients and Xterms (Linux or 
Putty probably).  Raw connections like Netcat or Putty in raw mode 
should work too, although you might see double echoing.  Oddball telnet 
clients and machines would be appreciated too.



Mike