I see a bit of info here: … ld-in-its-table
When I researched my issue online, I came across … kets-with-delay and someone indicated that I should use source-based routing, and someone else indicated that by using NAT (which what dosbox manual recommends), something funny happens with TCP which is probably why half the time packets aren't being passed through to DOSBOX. The only ways out in my case since the server ignores the TCP reset command is for me to either flood the connection with resets while setting the ACK to every value (That would be 4 million sends), or wait for a long time until the remote server makes a reset, or I could close and restart DOSBOX and all the networking and pray that works. In fact, in some cases, the packet driver (for dosbox) receives NOTHING despite tcpdump in linux showcasing that data is being sent to the dosbox NIC (of sl0). And so far with it, things are good when I connect to a server for the first time, but on subsequent connects, the server thinks I'm using an existing connection but I'm not. I didn't modify the MTU and that's because I'm trying to write my own DOS internet application.
#Dosbox online manuals
Ok so I tried the newer HTGET with same setup and this time I had to wait about 10 seconds for any output, then half the data appeared all at once, then I had to wait another 10 seconds, and I receive the rest of the data along with "null assignment detected".īut it seems that the speed setting helped but I don't know why the dosbox manuals for networking only advocated for 9600bps. The newest version was released in March 2020, and there were significant fixes to htget.
0 kommentar(er)
