Mac host unable to communicate with Linux guest

[Vigster]

I have running MacOS Mojave V10.14.2 :

Created custom host only adapter Vboxnet 2
10.10.10.1/24

added the host only adapter and then chose vboxnet2 and start vm

When I do the ip addr in the linux hosts its ip is 10,10.10.3 and ping 10.10.10.1 it fails from the the Mac host I tried to ssh to the 10.10.10.3 and can't connect. So I exported this vm and then import on VirtualBox running on windows 10 Machine with the same setup. I have not problems logging in through ssh or bring up the webpage the guest linux Server.

I brought up different Virtual guest and used bridged adapter and did not have any issues.

Just only with the Host only adapter.

I also took the same vm and used VMware Fusion and same setup for host only adapter and it worked with no issues. Not sure why I cannot get the host only adapter to work using custom network.

Pls help with any ideas.

Thank you

[mpack]

NAT uses the 10.x address range.

Host only adapters do not. They use the 192.x address range.

Confusing these ranges is likely to cause problems.

[Vigster]

I can do the same networks on windows PC running VirtualBox with no problems using the same vm that I have running on the Mac. Just only on the Mac version with Virtualbox. As long as the none of the networks are overlapping or not used in my home network. This configuration should work. Also I am not using any Nat in this configuration. I have other vms with address space that need to talk to this vm and don't want have to re-ip everything.


I created a new VM with the same settings and same result. I added a bridge adapter and was able to ssh access everything on the guest. Deleted all the host only adapters and created only 1 with the default ip space and was unable to access anything on the guest from the host.

[Vigster]

Brand new Vm - Can see was assigned a DHCP address on the same network as Host - VBOXNET1

vboxnet1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
ether 0a:00:27:00:00:01
inet 10.10.10.1 netmask 0xffffff00 broadcast 10.10.10.255

[socratis]

Please post the following:

1. The "VirtualBox.xml" file located in "/Users/<you>/Library/VirtualBox".
2. The recipe of the VM, the "<VM>.vbox" file. Right-click on the VM in the VirtualBox Manager, select "Show in Finder".
3. A complete "VBox.log", from a complete VM run:
   • Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
   • With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
   • Save only the first "VBox.log".

ZIP all three files and attach them to your response. See the "Upload attachment" tab below the reply form.

PS. You seem to have a HiDPI screen. Please reduce your screenshots to at least 50%, 72 DPI. Not all of us are fortunate enough to have a HiDPI display...

[Vigster]

Let me know if I missed anything. I tried to ping the 10.10.10.1 (host) - No response but I pinged the DHCP server 10.10.10.2 no issues. I even tried going to older version of Virtual box and same issue. Not sure has to do with MacOS Mojave.

Thank you all for help on this ..

[Vigster]

Upgrade to the lastest version and still same issue only with host only adapter. Still unable to ping the guest or any guests on the same host only network.

[socratis]

I want you to delete the 10.10.10.x network and let the guest ping with the 192.168.156.x one. Then tell me if you have a problem.

And please explain to me why the 10.10.10.x need, why? What's your LAN look like for your host. Is it in the same range perhaps?

[Vigster]

I tried that and still unable to communicate no matter what network i use for the host only adapter. I uninstalled and installed again. Reason is that the vm's i am using have a hard coded ip on the nic to use that network and if try and change the apps on the vm dont like it. but works fine in a windows setup only on mac.

[socratis]

It's definitely not a "Mac" thing. I'm on a Mac (OSX) since 10.6.8 and VirtualBox 3.x and I've never in all these years had such a problem.

With the default 192.168.56.x HostOnly network, create a new VM and download a bootable Linux ISO. Boot from that ISO and choose not to install it but to try it. Try to ping the guest in that case...

[Vigster]

Same issue. I only have an issue with host only adapter. Bridged adapter / Nat work with no issues. I can delete all the host only and recreate them and I can not ping guest to guest , guest to host or host to guest. The only thing that works is guest to DHCP server.

[socratis]

Post the 3 files that I asked before (VirtualBox.xml, <VM>.vbox and VBox.log) for the test, LiveVM.

Assign the HostOnly network to the LiveVM, start/ping the host/shutdown. That's the kind of log I'd like to see...

[Vigster]

here is the request files

[socratis]

I'm sorry, there must have been an error in translation, because I said:

Assign the HostOnly network to the LiveVM, start/ping the host/shutdown

And you did:

00:00:01.276906 [/Devices/e1000/0/LUN#0/Config/] (level 5)
00:00:01.276907   IfPolicyPromisc      <string>  = "allow-network" (cb=14)
00:00:01.276907   IgnoreConnectFailure <integer> = 0x0000000000000000 (0)
00:00:01.276908   Network              <string>  = "HostInterfaceNetworking-en0" (cb=28)

That's Bridged mode over en0, not the HostOnly network...

And you didn't even tell me if the ping worked or not...

[Vigster]

Sorry, it failed.. Attached is a screen shot of the vm using a host only adapter.