Menu

#278 Built-in packet driver not functional (data)

v1.0_(example)
open
nobody
None
5
2021-06-28
2021-06-28
Mike St
No

I am using DOSEMU 1.4.0.0 for linux.
I boot it with an MS-DOS 6.22 bootdisk found here:

https://www.allbootdisks.com/downloads/Disks/MS-DOS_Boot_Disk_Download47/Diskette%20Images/Dos6.22.img

I then download mTCP tools to assist me with my networking for DOS. Those tools are here:

http://www.brutman.com/mTCP/mTCP_2020-03-07.zip

So my goal is to grab an IP address from my router via DHCP (a tool included in mTCP).

Here are the tests I have done already and in each instance, the computer is connected to the router:

Test 1:
On a Dell Wyse Thin client, I installed the utilities above and loaded the Rhine packet driver. When I launch mTCP's DHCP, I get an IP address in a matter of seconds. It works every time.

Test 2:
On my laptop (that I'm using), I load DOSBOX 0.74 and installed mTCP, but I also followed the DOSBOX networking manual found here: https://www.dosbox.com/wiki/Slip_configuration_on_linux_host

This means once DOSBOX starts, the ETHERSL packet driver loads. This translates the virtual serial line that linux created into a DOS network. This setup works fine but I notice that the data transfer is slow, then again the link is over a 115200bps virtual line, but I'd like something faster.

So now on to what I'm struggling with now. Test 3 with DOSEMU:

I decide to modify the DOS boot disk so I can include mTCP tools and eliminate files I don't need. I then execute "dosemu -i" and tell it where the boot disk is. It loads the DOS environment as expected, but I notice something strange.

when I use mTCP tools to scan the driver with its command "pkttool scan", it names the driver "linux$" and it states the receive mode is all packets and the mac address seems to be valid.

If I use mTCP's DHCP tool to get an IP address automatically, it can't find an IP address for me, however all computers in all tests are connected to the exact same router which dishes out IP addresses when a computer asks for one. It can't be the router because the router has capacity to dish out at least 99 IP addresses at a time and there are less than 4 connections to the router.

I even tried rectifying the problem by specifying in the mTCP configuration the correct gateway IP address of my router and I still have no luck.

What do I do?

1 Attachments

Discussion


Log in to post a comment.