Host only adapter connection

[elewis33]

I'm attempting to setup a host-only adapter on my Oracle Linux VM (Redhat really). I have one adapter setup for NAT and another for host-only communications. In the past this has been a breeze but for the life of me I can't make it work with my current version of VirtualBox. I've read documentation, searched the forum and other sites and followed lots of instructions to make this happen, and I swear I have it setup correctly but my host simply will not connect to the guest network/port.

The host-only adapter is setup as a DHCP server, with appropriate subnet, gateway, IP min/max, etc. If you want to see configuration detail just let me know what you need to see and I'll be glad to run commands and provide output.

FYI, I'm running version 6.0.8 r130520 (Qt5.6.3) on Mac OS X Mojave 10.14.5 with an Oracle Linux 7 guest OS.

Are there any tricks to making these adapters work with the latest versions of VirtualBox? Or is this more related to the guest configuration (network adapters, firewall)? I've killed most of a day struggling with this and it's time to get some help. Help!

Earl

P.S. I've setup a serial port on the VM to capture the boot log from the guest, which is different from the VBox.log (right?). And I can send either one (or both) of those if they'd be useful.

[socratis]

and I swear I have it setup correctly but my host simply will not connect to the guest network/port

Can it ping it? Is pinging allowed?

If you want to see configuration detail just let me know what you need to see and I'll be glad to run commands and provide output

Sure...

• VBoxManage list hostonlyifs
  VBoxManage list dhcpservers
  

and from the guest the output of either of those commands, first one being favored:

• nmcli d show
  ifconfig -a
  

Are there any tricks to making these adapters work with the latest versions of VirtualBox?

Nope, they simply work, as they always have.

Or is this more related to the guest configuration (network adapters, firewall)?

That's actually the scenario with the most probabilities right now...

Finally, we need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• 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 it and attach it to your response. See the "Upload attachment" tab below the reply form.

[elewis33]

OK, startup and shutdown log attached and command output shown below. Also, I have verified that the network adapters on the guest are active and the config matches what's shown below. Thanks so much for taking a look at this.

>> Command output from host

Code: Select all

u0363644$ VBoxManage list hostonlyifs
Name:            vboxnet0
GUID:            786f6276-656e-4074-8000-0a0027000000
DHCP:            Disabled
IPAddress:       192.168.56.1
NetworkMask:     255.255.255.0
IPV6Address:     
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 0a:00:27:00:00:00
MediumType:      Ethernet
Wireless:        No
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-vboxnet0

u0363644$ VBoxManage list dhcpservers
NetworkName:    HostInterfaceNetworking-vboxnet0
IP:             192.168.56.2
NetworkMask:    255.255.255.0
lowerIPAddress: 192.168.56.3
upperIPAddress: 192.168.56.254
Enabled:        Yes
Global options:
   1:255.255.255.0

>> ran this from the host after the guest was up and running

Code: Select all

u0363644$ ping 192.168.156.3
PING 192.168.156.3 (192.168.156.3): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8

>> Command output from guest
>> nmcli d show

Code: Select all

GENERAL.DEVICE:                         eth0
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         08:00:27:8C:7A:C8
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (connected)
GENERAL.CONNECTION:                     System eth0
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/1
WIRED-PROPERTIES.CARRIER:               on
IP4.ADDRESS[1]:                         10.0.2.15/24
IP4.GATEWAY:                            10.0.2.2
IP4.ROUTE[1]:                           dst = 0.0.0.0/0, nh = 10.0.2.2, mt = 100
IP4.ROUTE[2]:                           dst = 10.0.2.0/24, nh = 0.0.0.0, mt = 100
IP4.DNS[1]:                             172.20.120.20
IP4.DOMAIN[1]:                          vpn.utah.edu
IP6.GATEWAY:                            --

GENERAL.DEVICE:                         virbr0
GENERAL.TYPE:                           bridge
GENERAL.HWADDR:                         52:54:00:8D:40:1E
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (connected)
GENERAL.CONNECTION:                     virbr0
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/3
IP4.ADDRESS[1]:                         192.168.122.1/24
IP4.GATEWAY:                            --
IP4.ROUTE[1]:                           dst = 192.168.122.0/24, nh = 0.0.0.0, mt = 0
IP6.GATEWAY:                            --

GENERAL.DEVICE:                         eth1
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         08:00:27:63:B2:53
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (connected)
GENERAL.CONNECTION:                     Profile 1
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/2
WIRED-PROPERTIES.CARRIER:               on
IP4.ADDRESS[1]:                         192.168.56.3/24
IP4.GATEWAY:                            --
IP4.ROUTE[1]:                           dst = 192.168.56.0/24, nh = 0.0.0.0, mt = 101
IP6.GATEWAY:                            --

GENERAL.DEVICE:                         lo
GENERAL.TYPE:                           loopback
GENERAL.HWADDR:                         00:00:00:00:00:00
GENERAL.MTU:                            65536
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
IP4.ADDRESS[1]:                         127.0.0.1/8
IP4.GATEWAY:                            --
IP6.GATEWAY:                            --

GENERAL.DEVICE:                         virbr0-nic
GENERAL.TYPE:                           tun
GENERAL.HWADDR:                         52:54:00:8D:40:1E
GENERAL.MTU:                            1500
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --

[elewis33]

Oops! Pinged the wrong address. Still doesn't respond.

u0363644$ ping 192.168.56.3
PING 192.168.56.3 (192.168.56.3): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8

[socratis]

Your guest is getting an appropriate IP address:
[quote=""VBoxManage list dhcpservers""]

lowerIPAddress: 192.168.56.3

[/quote][quote=""nmcli d show""]

IP4.ADDRESS[1]: 192.168.56.3/24

[/quote]
Now, why you can't ping, that's another story, a story that you'd have to look from within the configuration of your guest. As far as I can tell, VirtualBox's HostOnly DHCP server is alive and working as it should...