Re: [Freedos-user] Virtualbox Networking Issue

[Ralf Quint]

On 5/27/2021 12:06 PM, Michael Brutman wrote:


Ralf: Traceroute is interesting, and it's on the todo list.  This is 
more equivalent to a TCPDUMP trace.


Yeah, that would be really helpful. As I mentioned, ping (without any 
such logging enabled) isn't really a diagnostic tool. It just tells you 
THAT a connection failed (which you already know, hence you are 
troubleshooting). A traceroute at least will tell you (in most cases) 
WHERE it fails and depending on what that host is (the blackhole IP in 
this case didn't come back as a DNS server when I made a quick test this 
morning), and that helps to determine the next possible step(s) in 
fixing any networking issue...


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

[Michael Brutman]

Kelley: That version of mTCP is nearly 8 years old ...  Please get the
current version and repeat the trace file steps.  It might even just work
without debugging ...  I've made a lot of reliability improvements in the
past 8 years.  Also, please email me *directly* ...  this is an mTCP
question, not a FreeDOS question.  Other people might be able to help, but
I'm the best qualified and I check my email more often than I check this
mailing list.

In this trace:

   - The NAMESERVER_PREFERRED setting didn't exist back then.  It is using
   your ISP as the nameserver.
   - Your machine received an ARP response, so that part is nice - you have
   connectivity to your gateway.
   - Try pinging your nameserver directly (67.168.138.6).  If you can't get
   a response, then DNS won't ever work.


Ralf: Traceroute is interesting, and it's on the todo list.  This is more
equivalent to a TCPDUMP trace.



On Thu, May 27, 2021 at 10:14 AM Ralf Quint  wrote:

> On 5/26/2021 10:17 PM, Kelley McChesney wrote:
>
> 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.
>
> Just had a look at that log file and it seems the data gets stuck at
> 67.158.138.6. That is not the IP address for the site pinged, so that is
> where you're problem lies (your router?, the address range refers to
> bentcom.net).
>
> In either case, this is a public IP address and already outside of your
> (FreeDOS) box...
>
> Ralf
>
>
>
>
> --
> [image: Avast logo] 
>
> This email has been checked for viruses by Avast antivirus software.
> www.avast.com 
>
> <#m_-8092473799975067297_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> ___
> 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

[Ralf Quint]

On 5/26/2021 10:17 PM, Kelley McChesney wrote:

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.
Just had a look at that log file and it seems the data gets stuck at 
67.158.138.6. That is not the IP address for the site pinged, so that is 
where you're problem lies (your router?, the address range refers to 
bentcom.net).


In either case, this is a public IP address and already outside of your 
(FreeDOS) box...


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

[Ralf Quint]

On 5/26/2021 8:04 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.


Is that some kind of "traceroute in disquise"? Any chance to add a 
traceroute program to the mTCP package?


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

[Kelley McChesney]

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

[Michael Brutman]

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

[Eric Auer]

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] Virtualbox Networking Issue

[Kelley McChesney]

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

[Ralf Quint]

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

[Kelley McChesney]

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

[Eric Auer]

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] Virtualbox Networking Issue

[Kelley McChesney]

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

Re: [Freedos-user] Virtualbox Networking Issue

[Jerome Shidel]

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] Virtualbox Networking Issue

[Kelley McChesney]

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