TCP/IP Testing help, Round 2
Gordon JC Pearce
gordon at gjcp.net
Mon Jan 1 11:39:11 CST 2007
Michael B. Brutman wrote:
> Happy New Year!
> I'm back at it again - I plan on doing better this time. (I've fixed
> the specific double delete bug that bit me last time, improved tracing
> quite a bit, and added a lot of consistency checking code.)
Works for me
> Just like last time, all you need to do is telnet to 184.108.40.206,
> port 2301. Once again, that's my Linux box, but today it is forwarding
> port 2301 to my PCjr. The commands are slightly enhanced from the last
> test, but it isn't anything highly interactive.
> Up to 9 people can connect simultaneously. We didn't get more than 2 or
> 3 simultaneous connections last time, so I'm probably overly optimistic.
I can leave a telnet session connected indefinitely, if it won't time out...
> Some of you noted from last time that there is no character echoing or
> line editing. Telnet users on Unix machines will probably have local
> line editing, which makes things a wee bit nicer. The standard Windows
> telnet client doesn't do that by default, so you will type but not see
> your characters. That's a project for a different day.
> Here is a picture of the machine you are connecting to, complete with
> the Western Digital 8003 Ethernet card grafted onto the side:
> And lastly, if you remember, type in your OS and machine type as a
> command. It will complain about it being an invalid command, but I'll
> see it in the log and I'll have a better idea of what I'm testing against.
More information about the cctech