345 karma · joined November 10, 2021
The DOS TSR approach would make TCP/IP a common service for DOS programs. I went with the library approach for speed and customization purposes.
Other notable cards for older machines include the NE1000 (8 bit), NE2000, Intel 8/16, Western Digital or SMC 8000 series. Many PCI cards work well; just look for a packet driver. For those of you without real slots the Xircom PE3-10BT device is great, but they are getting more expensive in the wild.
SLIP and PPP work. PLIP works too, but I have not tested it myself.
And there are even packet drivers that allow for Token Ring and Arcnet to be used; they emulate Ethernet.
What I have now can best be described as cooperative multitasking with custom contexts. Example: the FTP server and HTTP server keep track of each user connection, provide them a buffer, and know the state of the session and how far into the file they are that is being transferred. (True multithreading would generalize that kind of context as a set of registers and a stack for each thread.)
Applications include fresh implementations of a DHCP client, FTP client and server, HTTP server, IRC client, Telnet Client, SNTP client, Ping, and some other goodies. (These are not stale ports of old code.) Everything runs in 16 bit DOS and the library is open source.
The target is retro-computing hobbyists and people stuck with embedded solutions that use DOS. A good FTP client can be a godsend in that situation.
I prefer to look at DOS as "stable."
The machine is an IBM PCjr which was introduced in 1983. The machine is an Intel 8088 running at 4.77Mhz. A jrIDE sidecar has been added to add an IDE interface and fill the system memory out. Storage is a 4GB CF card on the IDE interface. A Xircom PE3-10BT Ethernet adapter is attached to the parallel port, which has been modified to be bi-directional. The floppy drive has been upgraded to a 720KB double density drive, but that was not really necessary as the machine boots and runs from the CF card.
Software is IBM PC DOS 5.02 and mTCP. I run the HTTP server as a long term test of the underlying TCP/IP code. (Another mTCP release is due soon.) Up to eight concurrent connections are supported, but each one slows the others down as they are sharing CPU time and network bandwidth.
My router is setup to use dynamic DNS and the machine is hidden behind the router. So it is not exposed to all of the badness of the open Internet, but it still is dealing with bots probing for PHP, Wordpress and other vulnerabilities on port 80.
The machine is capable of much better performance (2x) when a proper Ethernet card is used; the Xircom is bottlenecked by the parallel port. I only have one PCjr bus-to-ISA bus adapter and I did not want to tie it up while I am working on designing a new one.
For monitoring I have it broadcasting a UDP packet for each log entry that it makes. So there is a local disk log, and I can snoop on it from another machine in the house. This lets me run it without a monitor while still being able to check on it.
The machine has been up and running over 120 hours now. If you follow the status page from the main page you can see the real-time stats, including dropped packets, objects served, etc. If you look carefully you will see that my own internal network is quite noisy and that is giving it more to contend with.
I intend to run the machine this way indefinitely, with the occasional maintenance window. I don't expect the machine to weather a DOS attack. If it stays running and does not crash that is a victory.
More details on the Reddit post: https://www.reddit.com/r/vintagecomputing/comments/uptyr1/be...
Bonus: Make the machine beep! Every time it serves an object it beeps.
The content is reasonable for retro-computing. The numbers on the status page going up are priceless. :)
I wrote it back in 2014 and I've hosted brutman.com on it at times. My usual machine to run it on for torture testing is a PCjr with a hard drive and Ethernet. This 386 would be so much happier with an Ethernet card; the serial port connection is really hurting the performance.
A new version of mTCP is in the works; look for it in the next two months.
Keep in mind though that strata and accuracy are two different things. Presumably the further away from the high precision time device you are, the less precision you will get. Even though my PCjr is technically a stratum 1 server, the accuracy is miserable compared to real stratum 1 servers that are serving time that is in the microseconds range of accuracy.