virtualbox.org

Hi

A picture speaks a 1000 words so here is my picture of what I am trying to achieve, Is it possible ? See attached picture.

I am able to ping my Guest's Hostonly adapter IP address when my host Ubuntu does not have a IP to it, however when I try to give it an IP using DHCP I lose the ability to ping my VirtualBox guest's hostonly IP address.

When host ubuntu does not have IP
bala@bala-laptop:~$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:12

cd:b0:af
inet6 addr: fe80::bbbb:aaaa:fe18:a94f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:151981 errors:0 dropped:0 overruns:0 frame:0
TX packets:110240 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:192523623 (192.5 MB) TX bytes:13485268 (13.4 MB)
Interrupt:16
bala@bala-laptop:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.56.0 * 255.255.255.0 U 0 0 0 vboxnet0
bala@bala-laptop:~$ ping 192.168.56.101
PING 192.168.56.101 (192.168.56.101) 56(84) bytes of data.
64 bytes from 192.168.56.101: icmp_seq=6 ttl=64 time=11.1 ms
64 bytes from 192.168.56.101: icmp_seq=7 ttl=64 time=0.716 ms
64 bytes from 192.168.56.101: icmp_seq=8 ttl=64 time=0.661 ms
64 bytes from 192.168.56.101: icmp_seq=9 ttl=64 time=0.759 ms
64 bytes from 192.168.56.101: icmp_seq=10 ttl=64 time=0.617 ms

When host ubuntu does have IP

bala@bala-laptop:~$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:12

cd:b0:af
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::bbbb:aaaa:fe18:a94f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:151948 errors:0 dropped:0 overruns:0 frame:0
TX packets:110207 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:192517638 (192.5 MB) TX bytes:13479549 (13.4 MB)
Interrupt:16
bala@bala-laptop:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 1 0 0 eth0
192.168.56.0 * 255.255.255.0 U 0 0 0 vboxnet0
link-local * 255.255.0.0 U 1000 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
bala@bala-laptop:~$ ping 192.168.56.101
PING 192.168.56.101 (192.168.56.101) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted

Is there any way by which I can get an IP to my host interface and still be able to ping my Guest OS's host only interface?

I am posting information below to show how it should work/look. The only thing that I can think of that would keep you from being able to have the network active on the host is if the hosts address range was the same as the host-only service. They must be different. So the hosts actual network address can not be in the 192.168.56.* range.

-

Working host

Code: Select all

:~$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr ************** 
          inet addr:192.168.1.10  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr:**************/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2329606 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1117268 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3223009157 (3.2 GB)  TX bytes:104989601 (104.9 MB)
          Interrupt:43 Base address:0xc000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:328 (328.0 B)  TX bytes:328 (328.0 B)

vboxnet0  Link encap:Ethernet  HWaddr ************  
          inet addr:192.168.56.1  Bcast:192.168.56.255  Mask:255.255.255.0
          inet6 addr: fe80::800:27ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:214 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:68935 (68.9 KB)

:~$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
link-local      *               255.255.0.0     U     1000   0        0 eth0
192.168.1.0     *               255.255.255.0   U     1      0        0 eth0
192.168.56.0    *               255.255.255.0   U     0      0        0 vboxnet0

Working guest

Code: Select all

:~$ ifconfig -a
eth1      Link encap:Ethernet  HWaddr ************** 
          inet addr:192.168.56.101  Bcast:192.168.56.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fed7:7fd2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:53 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2048 (2.0 KB)  TX bytes:23729 (23.7 KB)

eth2      Link encap:Ethernet  HWaddr ************ 
          inet addr:10.0.3.15  Bcast:10.0.3.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe77:71ab/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:364 errors:0 dropped:0 overruns:0 frame:0
          TX packets:328 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:189853 (189.8 KB)  TX bytes:63994 (63.9 KB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:32 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:3089 (3.0 KB)  TX bytes:3089 (3.0 KB)

:~$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.0.3.0        *               255.255.255.0   U     1      0        0 eth2
192.168.56.0    *               255.255.255.0   U     1      0        0 eth1
link-local      *               255.255.0.0     U     1000   0        0 eth2
default         10.0.3.2        0.0.0.0         UG    0      0        0 eth2

Ping host -> guest

Code: Select all

perry@perry-desktop:~$ ping 192.168.56.101
PING 192.168.56.101 (192.168.56.101) 56(84) bytes of data.
64 bytes from 192.168.56.101: icmp_req=1 ttl=64 time=3.57 ms
64 bytes from 192.168.56.101: icmp_req=2 ttl=64 time=0.583 ms
64 bytes from 192.168.56.101: icmp_req=3 ttl=64 time=0.569 ms
64 bytes from 192.168.56.101: icmp_req=4 ttl=64 time=0.534 ms

Hi Perry,

I am having a similar configuration to what you have shown, however any idea as to why I am not able to ping the Guest's Hostonly adapter after acquiring an IP address on my host's eth0

Not with the information you have provided.
You have singled out a single adapter eth0 and what I need to see if the complete ifconfig from both host and guest
ifconfig -a would get the remaining information. Do this with the host connected.

Host machine's configuration
root@bala-laptop:/home/bala# ifconfig -a
eth0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet addr:123.234.23.87 Bcast:123.234.23.255 Mask:255.255.0.0
inet6 addr: fe80::223:xxxx:xxxx:a94f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:284331 errors:0 dropped:0 overruns:0 frame:0
TX packets:32063 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:47651540 (47.6 MB) TX bytes:4332480 (4.3 MB)
Interrupt:16

eth1 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet6 addr: fe80::xxx:xxxx:xxxx:cf01/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:17 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:777 errors:0 dropped:0 overruns:0 frame:0
TX packets:777 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:63577 (63.5 KB) TX bytes:63577 (63.5 KB)

vboxnet0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet addr:192.168.56.1 Bcast:192.168.56.255 Mask:255.255.255.0
inet6 addr: fe80::xxx:xxxx:xxxx:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:343 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:41626 (41.6 KB)

root@bala-laptop:/home/bala# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.56.0 * 255.255.255.0 U 0 0 0 vboxnet0
123.234.23.0 * 255.255.240.0 U 1 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
default 123.234.23.1 0.0.0.0 UG 0 0 0 eth0
root@bala-laptop:/home/bala#

Guest OS configuration

I am not able to copy off the virtual OS screen, so attached the same as screen shot.

This information shows a possible configuration error in the guest. IE: not receiving the host-only IPv4 address.

What is the guest?

From the host post the results of VBoxManage list hostonlyifs and VBoxManage list dhcpservers

Question: What is attached to eth1 on the host?

I will update as soon as I reach home today in next 6 hrs time.

bala@bala-laptop:~$ 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
Status: Down
VBoxNetworkName: HostInterfaceNetworking-vboxnet0

bala@bala-laptop:~$ VBoxManage list dhcpservers
NetworkName: HostInterfaceNetworking-vboxnet0
IP: 192.168.56.100
NetworkMask: 255.255.255.0
lowerIPAddress: 192.168.56.101
upperIPAddress: 192.168.56.254
Enabled: Yes

NetworkName: HostInterfaceNetworking-vboxnet2
IP: 0.0.0.0
NetworkMask: 0.0.0.0
lowerIPAddress: 0.0.0.0
upperIPAddress: 0.0.0.0
Enabled: No

bala@bala-laptop:~$

In my previous screenshot eth1 does not have an IP, Here I have shown that I have indeed have an IP.

bala@bala-laptop:~$ ping 192.168.56.101
PING 192.168.56.101 (192.168.56.101) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
^C
--- 192.168.56.101 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2001ms

bala@bala-laptop:~$ ping 192.168.56.100
PING 192.168.56.100 (192.168.56.100) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
^C
--- 192.168.56.100 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1007ms

bala@bala-laptop:~$ ping 192.168.56.1
PING 192.168.56.1 (192.168.56.1) 56(84) bytes of data.
64 bytes from 192.168.56.1: icmp_seq=1 ttl=64 time=0.074 ms
64 bytes from 192.168.56.1: icmp_seq=2 ttl=64 time=0.068 ms
^C
--- 192.168.56.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.068/0.071/0.074/0.003 ms
bala@bala-laptop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet addr:123.12.12.24 Bcast:123.12.12.255 Mask:255.255.240.0
inet6 addr: fe80::223:aaaa:bbbb:a94f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:28030 errors:0 dropped:0 overruns:0 frame:0
TX packets:3237 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4839944 (4.8 MB) TX bytes:502323 (502.3 KB)
Interrupt:16

eth1 Link encap:Ethernet HWaddr yy:yy:yy:yy:yy:yy
inet6 addr: fe80::224:bbbb:cccc:cf01/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:17 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:752 (752.0 B) TX bytes:752 (752.0 B)

vboxnet0 Link encap:Ethernet HWaddr 0a:00:27:00:00:00
inet addr:192.168.56.1 Bcast:192.168.56.255 Mask:255.255.255.0
inet6 addr: fe80::800:ffff:ffff:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:5174 (5.1 KB)

bala@bala-laptop:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.56.0 * 255.255.255.0 U 0 0 0 vboxnet0
123.12.12.0 * 255.255.240.0 U 1 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
default 123.12.12.1 0.0.0.0 UG 0 0 0 eth0
bala@bala-laptop:~$

I even tried to add a Route so that my connections to the host only adapter would go to the eth1 interface of my Guest OS, all in vain

root@bala-laptop:/home/bala# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.56.0 * 255.255.255.0 U 0 0 0 vboxnet0
123.12.12.0 * 255.255.240.0 U 1 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
default 123.12.12.1 0.0.0.0 UG 0 0 0 eth0
root@bala-laptop:/home/bala# ping 192.168.56.101
PING 192.168.56.101 (192.168.56.101) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
^C
--- 192.168.56.101 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1000ms

root@bala-laptop:/home/bala# route add -net 192.168.56.0/24 gw 192.168.56.1
root@bala-laptop:/home/bala# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.56.0 192.168.56.1 255.255.255.0 UG 0 0 0 vboxnet0
192.168.56.0 * 255.255.255.0 U 0 0 0 vboxnet0
123.12.12.0 * 255.255.240.0 U 1 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
default 123.12.12.1 0.0.0.0 UG 0 0 0 eth0
root@bala-laptop:/home/bala# ping 192.168.56.101
PING 192.168.56.101 (192.168.56.101) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
^C
--- 192.168.56.101 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1008ms

root@bala-laptop:/home/bala#

On doing a Zenmap scan I can see that the host is present, however I cannot attempt to connect to it.

NetworkName: HostInterfaceNetworking-vboxnet2
IP: 0.0.0.0
NetworkMask: 0.0.0.0
lowerIPAddress: 0.0.0.0
upperIPAddress: 0.0.0.0
Enabled: No

Why do you have this one? Look in the VirtualBox main manager and preferences -> network. Delete this one and try again.

When I looked up for this in the Graphical user Interface I cannot find the additional DHCP server under File > Preferences > network.

When I tried to issue the command as Root user, I am not able to see the additional HostInterfaceNetworking-vboxnet2 network.

root@bala-laptop:/home/bala# VBoxManage list dhcpservers
NetworkName: HostInterfaceNetworking-vboxnet0
IP: 192.168.56.100
NetworkMask: 255.255.255.0
lowerIPAddress: 192.168.56.101
upperIPAddress: 192.168.56.254
Enabled: Yes
root@bala-laptop:/home/bala#

When I tried as a normal user I found that and deleted that using command line as shown below, still no luck.

bala@bala-laptop:~$ VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet2
bala@bala-laptop:~$ VBoxManage list dhcpservers
NetworkName: HostInterfaceNetworking-vboxnet0
IP: 192.168.56.100
NetworkMask: 255.255.255.0
lowerIPAddress: 192.168.56.101
upperIPAddress: 192.168.56.254
Enabled: Yes

bala@bala-laptop:~$ ping 192.168.56.101
PING 192.168.56.101 (192.168.56.101) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
^C
--- 192.168.56.101 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999ms

From the hosts terminal type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use "" if the name has a space in it.

$ VBoxManage showvminfo SNORT --details
Name: SNORT
Guest OS: Debian
UUID: 1d722838-773c-4940-b8c3-07a93957ec54
Config file: /home/bala/VirtualBox VMs/SNORT/SNORT.vbox
Snapshot folder: /home/bala/VirtualBox VMs//SNORT/Snapshots
Log folder: /home/bala/VirtualBox VMs/SNORT/Logs
Hardware UUID: 1d722838-773c-4940-b8c3-07a93957ec54
Memory size: 756MB
Page Fusion: off
VRAM size: 12MB
CPU exec cap: 100%
HPET: off
Chipset: piix3
Firmware: BIOS
Number of CPUs: 1
Synthetic Cpu: off
CPUID overrides: None
Boot menu mode: message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI: on
IOAPIC: off
PAE: off
Time offset: 0 ms
RTC: UTC
Hardw. virt.ext: on
Hardw. virt.ext exclusive: on
Nested Paging: on
Large Pages: off
VT-x VPID: on
State: running (since 2011-11-24T14:14:55.141000000)
Monitor count: 1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Storage Controller Name (0): IDE Controller
Storage Controller Type (0): PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 2
Storage Controller Port Count (0): 2
Storage Controller Bootable (0): on
Storage Controller Name (1): SATA Controller
Storage Controller Type (1): IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1): 30
Storage Controller Port Count (1): 1
Storage Controller Bootable (1): on
IDE Controller (1, 0): Empty
SATA Controller (0, 0): /home/bala/VirtualBox VMs//SNORT/SNORT.vdi (UUID: 3a74b75c-17af-44ac-bf98-4ac67fa040db)
NIC 1: MAC: 0800273491B7, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny
NIC 1 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2: MAC: 08002706F7FC, Attachment: Host-only Interface 'vboxnet0', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
Audio: enabled (Driver: PulseAudio, Controller: AC97)
Clipboard Mode: Bidirectional
Video mode: 640x480x0
VRDE: disabled
USB: disabled
USB Device Filters:<none>
Available remote USB devices: <none>
Currently Attached USB Devices: <none>
Shared folders: <none>
VRDE Connection: not active
Clients so far: 0
Guest:
Configured memory balloon size: 0 MB
OS type: Debian
Additions run level: 0
Guest Facilities:
No active facilities.
$

virtualbox.org

[Solved] Need to ping Guest hostonly adapter from Host

[Solved] Need to ping Guest hostonly adapter from Host

Re: Need to ping Guest hostonly adapter from Host

Re: Need to ping Guest hostonly adapter from Host

Re: Need to ping Guest hostonly adapter from Host

Re: Need to ping Guest hostonly adapter from Host

Re: Need to ping Guest hostonly adapter from Host

Re: Need to ping Guest hostonly adapter from Host

Re: Need to ping Guest hostonly adapter from Host

Re: Need to ping Guest hostonly adapter from Host

Re: Need to ping Guest hostonly adapter from Host

Re: Need to ping Guest hostonly adapter from Host

Re: Need to ping Guest hostonly adapter from Host

Re: Need to ping Guest hostonly adapter from Host

Re: Need to ping Guest hostonly adapter from Host

Re: Need to ping Guest hostonly adapter from Host