One step forward, one back:

It seems I was wrong about the two machines behaving differently - they do
behave the same
The VMs in both cases can be reached from the outside world (ping in for
instance) when set to bridged mode

However, any attempt to ping out gives the original error

On Mon, Feb 10, 2020 at 9:42 PM Ben Barker <b...@bbarker.co.uk> wrote:

> Interestingly....problem does not seem to be bridged mode - same issue
> with NAT. Perhaps this is a virtualbox rather than a freedos issue....
>
> On Mon, Feb 10, 2020 at 9:42 PM Ben Barker <b...@bbarker.co.uk> wrote:
>
>> Not currently, but I plan to try another OS for comparison when I can
>>
>> On Mon, Feb 10, 2020 at 9:34 PM Jose Isaias Cabrera <jic...@outlook.com>
>> wrote:
>>
>>>
>>> Do you have any other "Non-freedos VM" that is working ok with "bridged
>>> mode"?
>>>
>>> ------------------------------
>>> *From:* Ben Barker <b...@bbarker.co.uk>
>>> *Sent:* Monday, February 10, 2020 04:27 PM
>>> *To:* Discussion and general questions about FreeDOS. <
>>> freedos-user@lists.sourceforge.net>
>>> *Subject:* Re: [Freedos-user] Bridged virtualbox adapter
>>>
>>> I haven't been usind DNS for now - just IP addresses
>>> On the machine that is working, I have set up Trumpet TCP and can ping
>>> out to the network, or in from the network
>>>
>>> On the other (using the same ova file on new hardware) I can ping
>>> 127.0.0.1, but any other destination returns "cannot resolve hosts
>>> hardware address"
>>>
>>> On both machines, when freeDos starts, I see:
>>>
>>> Packet Driver is at segment 03EE
>>> Interrupt number 0x9 (9)
>>> I/O port 0xD000 (53248)
>>> My ethernet address is <a mac address>
>>>
>>> That last line suggests that the MAC local MAC address is known....
>>> Running wireshark on the virtualbox host machine shows no evidence that
>>> traffic is leaving the VM at all
>>>
>>>
>>>
>>> On Mon, Feb 10, 2020 at 9:14 PM Jose Isaias Cabrera <jic...@outlook.com>
>>> wrote:
>>>
>>>
>>> Ben Barker, on Monday, February 10, 2020 03:57 PM, wrote...
>>> >
>>> > Cheers - yes I checked that. I think perhaps it is some oddity of the
>>> > host machine. On a different host (same subnet, same settings, but
>>> > different NIC hardware) it seems to work as expected
>>>
>>> Can you ping the name and the IP address from both places?
>>>
>>> Does nslookup for both machine and full DNS address return the same IP
>>> address?
>>>
>>> > But I have tried a few virtual adapters on this machine and when in
>>> > bridged mode all tell me "cannot resolve hosts hardware address"
>>> >
>>> > I have tried using Trumped and mTCP - so perhaps the issue is with the
>>> > packet driver / virtual adapter...
>>> >
>>> > On Mon, Feb 10, 2020 at 7:37 PM Louis Santillan <lpsan...@gmail.com>
>>> > wrote:
>>> >
>>> >     Are your `IPADDR`, `NETMASK` & `GATEWAY` vars that which match the
>>> >     subnet of the Ubuntu machine?  `IPADDR` & the `ethernet address`
>>> >     should be unique from your Ubuntu machine's setting.
>>> >
>>> >     To compare, in Ubuntu, type `ip a` or `ifconfig`.
>>> >
>>> > On Mon, Feb 10, 2020 at 5:18 AM Alain Mouette <ala...@pobox.com>
>>> wrote:
>>> >     >
>>> >     > Use netbootdisk.com to setup your NIC
>>> >     >
>>> >     >
>>> >     > Em 10/02/2020 09:02, Ben Barker escreveu:
>>> >     >
>>> >     > Morning
>>> > > I have a freedos install running on virtualBox, with the host machine
>>> > being Ubuntu
>>> >     >
>>> >     > If I run the networking in NAT mode, all is fine
>>> >     >
>>> > > If I try "bridged mode", then at startup fDos sees the network
>>> adapter,
>>> > and reports:
>>> >     >
>>> >     > Interrupt number 0x9 (9)
>>> >     > I/O port -xD020 (53280)
>>> >     > My ethernet address is xxxxxxxx
>>> >     >
>>> >     > but any attempt to see the outside network gives the error:
>>> >     >
>>> >     > "cannot resolve host's hardware address"
>>> >     >
>>> >     > My mtcp.cfg is:
>>> >     >
>>> >     > PACKETINT 0x09 (tried a few values here...)
>>> >     > IPADDR xxxxx
>>> >     > NETMASK xxxxx
>>> >     > GATEWAY xxxxx
>>> >     > NAMESERVER xxxxx
>>> >     >
>>> >     > Any ideas...?
>>> >     >
>>> _______________________________________________
>>> 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

Reply via email to