> Right. I thought about it later and wondered what the other DOS
> stacks did. What does MS-NET
MS-NET is resident software, and AFAIR ping-able.
> or Trumpet do?
I have no idea.
> Probably the same thing
> as mTCP and WATTCP.
nope.
Tom
___
Right. I thought about it later and wondered what the other DOS
stacks did. What does MS-NET or Trumpet do? Probably the same thing
as mTCP and WATTCP. I remember using ping in DOS to ensure
connectivity to Gateways and DNS, but I wasn't running any servers so
there was little reason to ping
Read the documentation for whatever networking software you are using.
mTCP in particular is not a "resident" program, so your FreeDOS machine
will not respond to ping requests unless an mTCP program is actively
running. WATTCP programs have the same behavior.
Can you ping in the other direction? It may be that the bridged vmbr0
interface does not pass or there is nothing in the networking stack that
listens for ICMP packets.
See also
https://forum.proxmox.com/threads/solved-cant-ping-windows-vm.65736/
On Mon, Dec 19, 2022 at 2:42 AM Trever Noggle
That worked. Thank you. I did discover that I now have network access
in freedos but it does not respond to ping requests. There are no
firewall rules that would prevent this on my lan and I removed the check
in the firewall box in proxmox for this host. Is there something that
needs to be
I just setup Proxmox 7.3.3 to do some testing Brett Johnson. Had no
issues installing FD 1.3. Chose "OS Type" as "Other", switched
"Network Device" to "rtl8139" and "Firewall" as "1". Installed by
hand packages "FDNET", "MTCP", "CRYNWR". There's no option for
passthru or private on the
Has anyone been able to get networking to work in proxmox. No matter
what I try it says that physical networking is not supported at this time.
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
