This is a little premature, but I'm dying to see how it goes.
My little TCP/IP test program is running again. You cat get to it by doing:
telnet 24.159.200.228 2023
The program is a small server that accepts up to 9 incoming connections. It is not a telnet server, so it is dependent upon your telnet client doing local echoing. Things like backspacing can hose it up, so just retype a command if it doesn't understand the command. Command parsing is a little crude too, so avoid extra spaces, chars, etc. (Upper/lower case does not matter.)
The interesting thing to do is to use the 'sockets' command to see who else is on, and the 'stats' command to see how my TCP/IP stack is holding up. There is also a crude message sending ability - you can send small messages to other users. And lastly, there is a 'sysop page' function for those of you who remember the BBS era.
This is running on a 386-40 at the moment, and I'm tracing everything that comes in or out just in case there is a bug I need to capture. It will be running for a few hours - give it a shot!
Background: I'm testing a new TCP/IP stack that I started working on in Nov 2005. It uses a packet driver directly to talk on the network. Everything from the packet driver on up (ARP, IP, UDP and TCP) was written from scratch. The development language is Turbo C++ 3.0 for DOS, and I use a 386-40 for development. The code will run well on an 8088 class machine.
I run a public test like this periodically to try to flush out subtle bugs. Having multiple people from multiple machines and OSes try to use the code concurrently is a very good test. So while the end product that you see is almost trivial, there is a lot of work to make it run.
Thanks,
Mike
My little TCP/IP test program is running again. You cat get to it by doing:
telnet 24.159.200.228 2023
The program is a small server that accepts up to 9 incoming connections. It is not a telnet server, so it is dependent upon your telnet client doing local echoing. Things like backspacing can hose it up, so just retype a command if it doesn't understand the command. Command parsing is a little crude too, so avoid extra spaces, chars, etc. (Upper/lower case does not matter.)
The interesting thing to do is to use the 'sockets' command to see who else is on, and the 'stats' command to see how my TCP/IP stack is holding up. There is also a crude message sending ability - you can send small messages to other users. And lastly, there is a 'sysop page' function for those of you who remember the BBS era.
This is running on a 386-40 at the moment, and I'm tracing everything that comes in or out just in case there is a bug I need to capture. It will be running for a few hours - give it a shot!
Background: I'm testing a new TCP/IP stack that I started working on in Nov 2005. It uses a packet driver directly to talk on the network. Everything from the packet driver on up (ARP, IP, UDP and TCP) was written from scratch. The development language is Turbo C++ 3.0 for DOS, and I use a 386-40 for development. The code will run well on an 8088 class machine.
I run a public test like this periodically to try to flush out subtle bugs. Having multiple people from multiple machines and OSes try to use the code concurrently is a very good test. So while the end product that you see is almost trivial, there is a lot of work to make it run.
Thanks,
Mike