Re: [Freedos-user] Virtualbox Networking Issue
Hi Michael, I went through the instructions to enable debugging and pinged www.brutman.com. I have attached my MTCP config file and the trace.txt file for you. Thank you for looking at this. On Wed, May 26, 2021 at 11:05 PM Michael Brutman wrote: > Hi - I'm the author of mTCP. mTCP is shipped with FreeDOS but it is an > independent project. > > Please check the PDF, specifically the section on debugging. I'd like to > see a trace from your system when you are using a bridged Ethernet > connection. Use PING (the one that comes with mTCP), but specifying the > hostname should be fine for determining what your DNS problem is. > > The short story is do this: > >- set debugging=255 >- set logfile=trace.txt >- ping www.brutman.com > > Take trace.txt and then email it to me. After I see it I can tell you > what I think is going on and I can give you some hints on how to proceed. > Sending me your mTCP configuration file would also be helpful. > > > Mike > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > 2021-05-26 20:15:04.36 mTcp Version: May 23 2013 2021-05-26 20:15:04.36 PACKETINT=60 MAC=08.00.27.00.D1.E6 MTU=1500 2021-05-26 20:15:04.36 IPADDR=192.168.4.77 NETMASK=255.255.252.0 GATEWAY=192.168.4.1 2021-05-26 20:15:04.36 NAMESERVER=67.158.138.6 2021-05-26 20:15:04.47 DOS Version 7.10, Sleep calls enabled: int 0x28 1 int 0x2f:1680 0 2021-05-26 20:15:04.47 Dns: Sending query to 67.158.138.6 for www.brutman.com 2021-05-26 20:15:04.47 Udp: Send: Ip: 67.158.138.6 SrcPort: 57 DstPort: 53 PayloadLen: 33 PreAlloc: 1 2021-05-26 20:15:04.47 Packet: Sending 60 bytes, dumping 60 FF FF FF FF FF FF 08 00 27 00 D1 E6 08 06 00 01 '... 08 00 06 04 00 01 08 00 27 00 D1 E6 C0 A8 04 4D '..M FF FF FF FF FF FF C0 A8 04 01 6D 54 43 50 20 62 ..mTCP b 79 20 4D 20 42 72 75 74 6D 61 6E 00 y M Brutman. 2021-05-26 20:15:04.47 Arp: Sent req for 192.168.4.1 2021-05-26 20:15:04.47 Udp: Send: Ip: 67.158.138.6 SrcPort: 57 DstPort: 53 PayloadLen: 33 PreAlloc: 1 2021-05-26 20:15:04.47 Udp: Send: Ip: 67.158.138.6 SrcPort: 57 DstPort: 53 PayloadLen: 33 PreAlloc: 1 2021-05-26 20:15:04.47 Udp: Send: Ip: 67.158.138.6 SrcPort: 57 DstPort: 53 PayloadLen: 33 PreAlloc: 1 2021-05-26 20:15:04.47 Packet: Received 60 bytes, dumping 60 08 00 27 00 D1 E6 5C A5 BC BB 7F ED 08 06 00 01 ..'...\. 08 00 06 04 00 02 5C A5 BC BB 7F ED C0 A8 04 01 ..\. 08 00 27 00 D1 E6 C0 A8 04 4D 00 00 00 00 00 00 ..'..M.. 00 00 00 00 00 00 00 00 00 00 00 00 2021-05-26 20:15:04.47 Arp: reply from 192.168.4.1 2021-05-26 20:15:04.47 Arp: Placed 192.168.4.1 in slot 0 2021-05-26 20:15:04.47 Arp: reply satisfied pending req 2021-05-26 20:15:04.47 Udp: Send: Ip: 67.158.138.6 SrcPort: 57 DstPort: 53 PayloadLen: 33 PreAlloc: 1 2021-05-26 20:15:04.47 Packet: Sending 75 bytes, dumping 75 5C A5 BC BB 7F ED 08 00 27 00 D1 E6 08 00 45 00 \...'.E. 00 3D 00 04 00 00 FF 11 29 12 C0 A8 04 4D 43 9E .=..)MC. 8A 06 00 39 00 35 00 29 27 C0 03 E1 01 80 00 01 ...9.5.)'... 00 00 00 00 00 00 03 77 77 77 07 62 72 75 74 6D ...www.brutm 61 6E 03 63 6F 6D 00 00 01 00 01 an.com. 2021-05-26 20:15:06.45 W Dns: No activity, pushing again 2021-05-26 20:15:06.45 Dns: Resending initial query 2021-05-26 20:15:06.45 Dns: Sending query to 67.158.138.6 for www.brutman.com 2021-05-26 20:15:06.45 Udp: Send: Ip: 67.158.138.6 SrcPort: 57 DstPort: 53 PayloadLen: 33 PreAlloc: 1 2021-05-26 20:15:06.45 Packet: Sending 75 bytes, dumping 75 5C A5 BC BB 7F ED 08 00 27 00 D1 E6 08 00 45 00 \...'.E. 00 3D 00 05 00 00 FF 11 29 11 C0 A8 04 4D 43 9E .=..)MC. 8A 06 00 39 00 35 00 29 27 BF 03 E2 01 80 00 01 ...9.5.)'... 00 00 00 00 00 00 03 77 77 77 07 62 72 75 74 6D ...www.brutm 61 6E 03 63 6F 6D 00 00 01 00 01 an.com. 2021-05-26 20:15:08.42 W Dns: No activity, pushing again 2021-05-26 20:15:08.42 Dns: Resending initial query 2021-05-26 20:15:08.42 Dns: Sending query to 67.158.138.6 for www.brutman.com 2021-05-26 20:15:08.42 Udp: Send: Ip: 67.158.138.6 SrcPort: 57 DstPort: 53 PayloadLen: 33 PreAlloc: 1 2021-05-26 20:15:08.42 Packet: Sending 75 bytes, dumping 75 5C A5 BC BB 7F ED 08 00 27 00 D1 E6 08 00 45 00 \...'.E. 00 3D 00 06 00 00 FF 11 29 10 C0 A8 04 4D 43 9E .=..)MC. 8A 06 00 39 00 35 00 29 27 BE 03 E3 01 80 00 01 ...9.5.)'... 00 00 00 00 00 00 03 77 77 77 07 62 72 75 74 6D ...www.brutm 61 6E 03 63 6F 6D 00 00 01 00 01 an.com. 2021-05-26 20:15:10.40 W Dns: No activity, pushing again 2021-05-26 20:15:10.40 Dns: Resending initial query 2021-05-26 20:15:10.40 Dns: Sending query to 67.158.138.6 for www.brutman.com 2021-05-26 20:15:10.40 Udp: Send: Ip:
Re: [Freedos-user] Virtualbox Networking Issue
Hi - I'm the author of mTCP. mTCP is shipped with FreeDOS but it is an independent project. Please check the PDF, specifically the section on debugging. I'd like to see a trace from your system when you are using a bridged Ethernet connection. Use PING (the one that comes with mTCP), but specifying the hostname should be fine for determining what your DNS problem is. The short story is do this: - set debugging=255 - set logfile=trace.txt - ping www.brutman.com Take trace.txt and then email it to me. After I see it I can tell you what I think is going on and I can give you some hints on how to proceed. Sending me your mTCP configuration file would also be helpful. Mike ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Virtualbox Networking Issue
Hi again, > Hi Ralf, I actually can't use traceroute to find the problem. This is in a > VM and as far as I know traceroute doesn't exist for FreeDOS. According to http://www.bttr-software.de/freesoft/comm1.htm there is a traceroute (tracert) included with wattcp32. Other implementations could exist as well, but for example classic 16-bit Watt/TCP and Brutman's mTCP do not seem to include it. I probably overlooked a number of traceroutes. Regards, Eric ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FAT12
Daniel Sears composed on 2021-05-26 15:38 (UTC-0700): > The Wikipedia page says that FAT12 goes back to the early 80's, 1980 or so, when max HD size was 5MB or 10MB, and FAT12 was sufficient. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FAT12
In the end I created a second partition and put my payload file there. That worked, but before that I tried to extend the FAT12 partition with gparted but my copy (from Ubuntu 21.04) objected and said that FAT12 is no longer supported. The Wikipedia page says that FAT12 goes back to the early 80's, along with Huey Lewis and the News. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Virtualbox Networking Issue
Hi Ralf, I actually can't use traceroute to find the problem. This is in a VM and as far as I know traceroute doesn't exist for FreeDOS. I have tried other VMs and they seem to work fine with different OS's, so this is purely a FreeDOS issue. On Wed, May 26, 2021 at 5:09 PM Ralf Quint wrote: > On 5/26/2021 1:45 PM, Kelley McChesney wrote: > > Hi Eric, I've actually been trying DHCP, which seems to be fine. I > > tried your recommendations and tested both my router's gateway as a > > nameserver and checked what my host computer was using. Unfortunately, > > my host computer was using the same server as the DHCP server was > > giving FreeDOS and my router's gateway didn't work either. I did try > > pinging some other IP addresses besides 8.8.8.8 that are outside my > > network and I do seem to have a connection, so it must be a problem > > DNS-wise. > Don't use ping, that is a horrible diagnostic tool. It just tells you > what you already know, that a connection works or it doesn't. > > Try using traceroute (tracert in Windows) to find out WHERE > data/connection is being lost... > > Ralf > > > > -- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Virtualbox Networking Issue
On 5/26/2021 1:45 PM, Kelley McChesney wrote: Hi Eric, I've actually been trying DHCP, which seems to be fine. I tried your recommendations and tested both my router's gateway as a nameserver and checked what my host computer was using. Unfortunately, my host computer was using the same server as the DHCP server was giving FreeDOS and my router's gateway didn't work either. I did try pinging some other IP addresses besides 8.8.8.8 that are outside my network and I do seem to have a connection, so it must be a problem DNS-wise. Don't use ping, that is a horrible diagnostic tool. It just tells you what you already know, that a connection works or it doesn't. Try using traceroute (tracert in Windows) to find out WHERE data/connection is being lost... Ralf -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Virtualbox Networking Issue
Hi Eric, I've actually been trying DHCP, which seems to be fine. I tried your recommendations and tested both my router's gateway as a nameserver and checked what my host computer was using. Unfortunately, my host computer was using the same server as the DHCP server was giving FreeDOS and my router's gateway didn't work either. I did try pinging some other IP addresses besides 8.8.8.8 that are outside my network and I do seem to have a connection, so it must be a problem DNS-wise. On Wed, May 26, 2021 at 4:28 PM Eric Auer wrote: > > Hi! > > > Unfortunately it does actually seem to be a networking issue. I just > tried > > to wget the current fdnpkg file from ibiblio.org and it failed, > reporting: > > "Resolving www.ibiblio.org... failed: No address associated with > hostname. > > Note that 8.8.8.8 is a nameserver outside your house, you could try > to set the IP of your network router or modem as nameserver. Those > often provide DNS proxy or cache services. Also, you could try DHCP, > which automatically asks the local network for suitable configuration. > > In DOS, the disadvantage of DHCP is that it might have to ask again > for each network access, because there is no permanently active DOS > network running in the background: Only apps themselve use the net. > > One idea would be to check another Linux or Windows computer in your > network to see which setting those use and derive one for DOS from it. > > Regards, Eric > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Virtualbox Networking Issue
Hi! > Unfortunately it does actually seem to be a networking issue. I just tried > to wget the current fdnpkg file from ibiblio.org and it failed, reporting: > "Resolving www.ibiblio.org... failed: No address associated with hostname. Note that 8.8.8.8 is a nameserver outside your house, you could try to set the IP of your network router or modem as nameserver. Those often provide DNS proxy or cache services. Also, you could try DHCP, which automatically asks the local network for suitable configuration. In DOS, the disadvantage of DHCP is that it might have to ask again for each network access, because there is no permanently active DOS network running in the background: Only apps themselve use the net. One idea would be to check another Linux or Windows computer in your network to see which setting those use and derive one for DOS from it. Regards, Eric ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FAT12
On 5/25/2021 7:00 PM, Michał Dec wrote: FAT12 sucks. The smallest pendrive I saw was 128MB and that was 18 years ago which is still 4x the size of FAT12's limit. Here's how you can force the installer to use an existing FAT16/FAT32 filesystem. This procedure will cause the installer to detect a valid DOS partition and skip the partitioning part and proceed to install. FAT12 does't suck. It works just perfectly fine for floppy disk, where it is even preferable to FAT16. The reason why the OP sees that partition is a bug in FDisk which has been discussed ad nauseam here on the list and is already fixed with a newer version of FDisk, thanks to Tom Ehlert, and all the other discussion about this is absolutely pointless... Ralf -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FAT12
On 5/25/2021 2:53 PM, Daniel Sears wrote: I've installed FreeDOS 1.3-RC4 with FD13LITE.img on a 4GB USB drive. This works and I can boot it just fine, but the primary partition uses FAT12 and is 97% full. I would like to expand this partition with gparted, but that no longer supports FAT12. Can I ask what the rationale is for using FAT12? It's a bug in the version of FDisk included and has been discussed here on the list in length... Ralf -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Virtualbox Networking Issue
Unfortunately it does actually seem to be a networking issue. I just tried to wget the current fdnpkg file from ibiblio.org and it failed, reporting: "Resolving www.ibiblio.org... failed: No address associated with hostname. wget.exe: unable to resolve host address 'www.ibiblio.org'". I did forget to mention this in my first email but I did previously try adding 8.8.8.8 as a NAMESERVER_PREFERRED in the MTCP config file but it had the same problem. On Wed, May 26, 2021 at 1:58 AM Jerome Shidel wrote: > Since you had ping working, you probably had networking working. > > So, it may just be an issue with the config file for FDNPKG that got > installed. You should verify the settings in C:\FDOS\BIN\FDNPKG.CFG or you > can just fetch the latest version of the package from the online repository > at > http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.2/pkg-html/fdnpkg.html > and > use unzip and update that config and binary by hand. > > On May 25, 2021, at 8:20 PM, Kelley McChesney > wrote: > > > Hi, > > I was having trouble getting my network setup with FreeDOS 1.2 on > Virtualbox. I installed FDNet, Ping, and MTCP after installation, but after > rebooting, I get strange network issues. I have tried both Bridged and NAT > networking. With bridged, I get a DHCP connection and can ping IP > addresses, but when I try to connect to any web address (mainly just > running 'fdnpkg update'), it will try to connect for about a minute then > says 'Repository download failed!'. With NAT, it is similar, but I cannot > ping any IP addresses and fdnpkg returns the same issue instantaneously > without waiting 30 seconds. Anyone have an idea what could be the issue? > > Thanks, Kelley > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
