[Resolved] Host-only network stops working, when connecting to 192.168.x.x IP-network (#18857)

Discussions related to using VirtualBox on Windows hosts.

Re: Host-only network stops working, when connecting to specific cable

Postby scottgus1 » 19. Aug 2019, 14:49

Please deliver the information asked if you wish to get us to try to help. If you no longer wish to have us try, and you do not wish to post the requested information, please post one more time saying you no longer require help and wish to stop this thread.

scottgus1 wrote:Shut down your guest.
Connect your PC to Corp. Run "ipconfig /all" on the host. Start the guest. Let it stabilize then run "ifconfig" on the guest. Please post the outputs of these two commands, labeling each.

Shut down your guest again.
Connect your PC to RD. Run "ipconfig /all" on the host. Start the guest. Let it stabilize then run "ifconfig" on the guest. Please post the outputs of these two commands, labeling each.

fth0 wrote:@Stradman:
Can you also provide PCAP files from the guest and from the host, capturing all network interfaces on the host simultaneously?

socratis wrote:If ZIPPING them doesn't get you down below the 128 KB limit, then an external site is your only option. For example, in the following site your file is available for 30 days, limit 5 GB, no registration required: https://uploadfiles.io/

fth0 wrote:When issuing the "ipconfig /all" command, also issue a "route print" command to show the current routing table on the host.

You do see that many attempts to get useful diagnostic data have been made.
Stradman wrote:There should not be any IP overlaps in the current setup,

No way for us to verify that, and just because it is written on the internet does not necessarily make it true.

fth0 wrote:If you like to have a 2nd opinion, you should deliver the information that you have been interpreting only yourself.

I agree exactly.

Stradman wrote:I am not quite sure about how much information I can share on specific details here from the corporation.

Private IP addresses are not hackable. If you are worried, ask your IT folks. But to get further help you will need to give us something solid to go on. And you have not done that yet.

FWIW if Host-Only works on one network and does not work on the other network, then it's the other network's fault, not Virtualbox's.
Human government is like that crazy uncle who hides a quarter in his fist behind his back, then asks you to guess which fist the quarter is in...
No matter which side you choose, Left or Right, both Sides are empty.
scottgus1
 
Posts: 4262
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Win7

Re: Host-only network stops working, when connecting to specific cable

Postby Stradman » 19. Aug 2019, 15:13

RD NETWORK

HOST
Code: Select all   Expand viewCollapse view
>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : FITMP1-L4841
   Primary Dns Suffix  . . . . . . . : mcint.local
   Node Type . . . . . . . . . . . . : Peer-Peer
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : mcint.local

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) Ethernet Connection (5) I219-LM
   Physical Address. . . . . . . . . : 8C-16-45-5A-BC-D4
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.119.12(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.224.0
   Lease Obtained. . . . . . . . . . : maanantai 19. elokuuta 2019 14.33.49
   Lease Expires . . . . . . . . . . : maanantai 19. elokuuta 2019 17.03.49
   Default Gateway . . . . . . . . . : 192.168.100.1
   DHCP Server . . . . . . . . . . . : 192.168.101.201
   DNS Servers . . . . . . . . . . . : 192.168.101.201
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
   Physical Address. . . . . . . . . : 0A-00-27-00-00-0A
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 172.16.0.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.240.0.0
   Default Gateway . . . . . . . . . :
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Npcap Loopback Adapter:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Npcap Loopback Adapter
   Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::68cc:d17e:a70c:4b3d%7(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.75.61(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 1107427404
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-24-41-E3-D7-8C-16-45-5A-BC-D4
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled


>route print

Interface List
  8...8c 16 45 5a bc d4 ......Intel(R) Ethernet Connection (5) I219-LM
 10...0a 00 27 00 00 0a ......VirtualBox Host-Only Ethernet Adapter
  7...02 00 4c 4f 4f 50 ......Npcap Loopback Adapter
 18...a0 c5 89 a5 91 a0 ......Intel(R) Dual Band Wireless-AC 8265
 14...a0 c5 89 a5 91 a1 ......Microsoft Wi-Fi Direct Virtual Adapter
 13...a2 c5 89 a5 91 a0 ......Microsoft Wi-Fi Direct Virtual Adapter #2
  1...........................Software Loopback Interface 1


>ping 172.16.0.101

Pinging 172.16.0.101 with 32 bytes of data:
Reply from 172.16.0.101: bytes=32 time<1ms TTL=64
Reply from 172.16.0.101: bytes=32 time<1ms TTL=64
Reply from 172.16.0.101: bytes=32 time<1ms TTL=64
Reply from 172.16.0.101: bytes=32 time<1ms TTL=64

Ping statistics for 172.16.0.101:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Code: Select all   Expand viewCollapse view
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    192.168.100.1   192.168.119.12     25
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
      169.254.0.0      255.255.0.0         On-link     169.254.75.61    281
    169.254.75.61  255.255.255.255         On-link     169.254.75.61    281
  169.254.255.255  255.255.255.255         On-link     169.254.75.61    281
       172.16.0.0      255.240.0.0         On-link        172.16.0.1    281
       172.16.0.1  255.255.255.255         On-link        172.16.0.1    281
   172.31.255.255  255.255.255.255         On-link        172.16.0.1    281
     192.168.96.0    255.255.224.0         On-link    192.168.119.12    281
   192.168.119.12  255.255.255.255         On-link    192.168.119.12    281
  192.168.127.255  255.255.255.255         On-link    192.168.119.12    281
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
        224.0.0.0        240.0.0.0         On-link        172.16.0.1    281
        224.0.0.0        240.0.0.0         On-link     169.254.75.61    281
        224.0.0.0        240.0.0.0         On-link    192.168.119.12    281
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link        172.16.0.1    281
  255.255.255.255  255.255.255.255         On-link     169.254.75.61    281
  255.255.255.255  255.255.255.255         On-link    192.168.119.12    281
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    331 ::1/128                  On-link
  7    281 fe80::/64                On-link
  7    281 fe80::68cc:d17e:a70c:4b3d/128
                                    On-link
  1    331 ff00::/8                 On-link
  7    281 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

GUEST
Code: Select all   Expand viewCollapse view
$ ifconfig -a

enp0s3    Link encap:Ethernet  HWaddr 08:00:27:20:cc:68 
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:47596 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21490 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:63532672 (63.5 MB)  TX bytes:1562889 (1.5 MB)

enp0s8    Link encap:Ethernet  HWaddr 08:00:27:55:df:60 
          inet addr:172.16.0.101  Bcast:172.31.255.255  Mask:255.240.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:186 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2440 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:35188 (35.1 KB)  TX bytes:235747 (235.7 KB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:474 errors:0 dropped:0 overruns:0 frame:0
          TX packets:474 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:40780 (40.7 KB)  TX bytes:40780 (40.7 KB)


$ route -n
Kernel IP routing table
[pre]Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.0.2.2        0.0.0.0         UG    100    0        0 enp0s3
10.0.2.0        0.0.0.0         255.255.255.0   U     100    0        0 enp0s3
172.16.0.0      0.0.0.0         255.240.0.0     U     100    0        0 enp0s8[/pre]


$ ping 172.16.0.1
PING 172.16.0.1 (172.16.0.1) 56(84) bytes of data.


Private IP addresses are not hackable. If you are worried, ask your IT folks. But to get further help you will need to give us something solid to go on. And you have not done that yet.

Well, I did not specifically mention my worry about the IP-addresses... It's the PCAPs that might contain unprotected sensitive data, hence not posting yet.


FWIW if Host-Only works on one network and does not work on the other network, then it's the other network's fault, not Virtualbox's.

I'm hoping this turns out that simple. But, having worked with both networks and software for some time now, I would not play fast'n'loose either way, yet. Keyword: "bug".
Last edited by socratis on 20. Aug 2019, 04:28, edited 3 times in total.
Reason: Enclosed the information in [quote][code] tags for better readability
Stradman
 
Posts: 18
Joined: 16. Aug 2019, 11:51

Re: Host-only network stops working, when connecting to specific cable

Postby Stradman » 19. Aug 2019, 15:36

Stradman wrote:I did already the NIC tracing, before posting the thread, but the PCAP trace did not reveal anything useful to me..

For further tracing I was asking if there are developer logs from the code, that I could check or provide..

socratis wrote:No, there not more. But I'll agree and reiterate what mpack said: it doesn't make any sense, unless there's a conflict of network ranges. Let's see if our network guru-users have anything more to say on the matter. I can't even read PCAPs... ;)

Apparently there is, but no beginners guide, or direct examples how to use this:
https://www.virtualbox.org/manual/ch08. ... ge-debugvm
https://www.virtualbox.org/wiki/VBoxLogging
https://www.virtualbox.org/browser/vbox ... DrvTAP.cpp

(Not sure if DrvTAP.cpp is the correct place to look here, but just to point out that there are traces that can be taken of the VBox execution..)
Stradman
 
Posts: 18
Joined: 16. Aug 2019, 11:51

Re: Host-only network stops working, when connecting to specific cable

Postby scottgus1 » 19. Aug 2019, 15:40

Thanks for the info, Stradman. Which of the two networks was this info for? Corp or RD?
Please post the same info when connected to the other network, too. Please reboot the guest after connecting to the other network.
Human government is like that crazy uncle who hides a quarter in his fist behind his back, then asks you to guess which fist the quarter is in...
No matter which side you choose, Left or Right, both Sides are empty.
scottgus1
 
Posts: 4262
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Win7

Re: Host-only network stops working, when connecting to specific cable

Postby Stradman » 19. Aug 2019, 15:47

CORP NETWORK

HOST
Code: Select all   Expand viewCollapse view
>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : FITMP1-L4841
   Primary Dns Suffix  . . . . . . . : mcint.local
   Node Type . . . . . . . . . . . . : Peer-Peer
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : mcint.local

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : mcint.local
   Description . . . . . . . . . . . : Intel(R) Ethernet Connection (5) I219-LM
   Physical Address. . . . . . . . . : 8C-16-45-5A-BC-D4
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 134.37.124.236(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : maanantai 19. elokuuta 2019 16.41.51
   Lease Expires . . . . . . . . . . : sunnuntai 25. elokuuta 2019 16.41.51
   Default Gateway . . . . . . . . . : 134.37.124.1
   DHCP Server . . . . . . . . . . . : 134.37.4.4
   DNS Servers . . . . . . . . . . . : 134.37.1.53
                                       134.37.1.52
                                       134.37.131.65
                                       134.37.24.222
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
   Physical Address. . . . . . . . . : 0A-00-27-00-00-0A
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 172.16.0.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.240.0.0
   Default Gateway . . . . . . . . . :
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Npcap Loopback Adapter:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Npcap Loopback Adapter
   Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::68cc:d17e:a70c:4b3d%7(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.75.61(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 1107427404
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-24-41-E3-D7-8C-16-45-5A-BC-D4
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled


>route print

Interface List
  8...8c 16 45 5a bc d4 ......Intel(R) Ethernet Connection (5) I219-LM
 10...0a 00 27 00 00 0a ......VirtualBox Host-Only Ethernet Adapter
  7...02 00 4c 4f 4f 50 ......Npcap Loopback Adapter
 14...a0 c5 89 a5 91 a1 ......Microsoft Wi-Fi Direct Virtual Adapter
 13...a2 c5 89 a5 91 a0 ......Microsoft Wi-Fi Direct Virtual Adapter #2
 18...a0 c5 89 a5 91 a0 ......Intel(R) Dual Band Wireless-AC 8265
  1...........................Software Loopback Interface 1


>ping 172.16.0.101

Pinging 172.16.0.101 with 32 bytes of data:
Reply from 172.16.0.101: bytes=32 time<1ms TTL=64
Reply from 172.16.0.101: bytes=32 time<1ms TTL=64
Reply from 172.16.0.101: bytes=32 time<1ms TTL=64
Reply from 172.16.0.101: bytes=32 time<1ms TTL=64

Ping statistics for 172.16.0.101:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Code: Select all   Expand viewCollapse view
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0     134.37.124.1   134.37.124.236     25
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
     134.37.124.0    255.255.255.0         On-link    134.37.124.236    281
   134.37.124.236  255.255.255.255         On-link    134.37.124.236    281
   134.37.124.255  255.255.255.255         On-link    134.37.124.236    281
      169.254.0.0      255.255.0.0         On-link     169.254.75.61    281
    169.254.75.61  255.255.255.255         On-link     169.254.75.61    281
  169.254.255.255  255.255.255.255         On-link     169.254.75.61    281
       172.16.0.0      255.240.0.0         On-link        172.16.0.1    281
       172.16.0.1  255.255.255.255         On-link        172.16.0.1    281
   172.31.255.255  255.255.255.255         On-link        172.16.0.1    281
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
        224.0.0.0        240.0.0.0         On-link        172.16.0.1    281
        224.0.0.0        240.0.0.0         On-link     169.254.75.61    281
        224.0.0.0        240.0.0.0         On-link    134.37.124.236    281
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link        172.16.0.1    281
  255.255.255.255  255.255.255.255         On-link     169.254.75.61    281
  255.255.255.255  255.255.255.255         On-link    134.37.124.236    281
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    331 ::1/128                  On-link
  7    281 fe80::/64                On-link
  7    281 fe80::68cc:d17e:a70c:4b3d/128
                                    On-link
  1    331 ff00::/8                 On-link
  7    281 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

GUEST
Code: Select all   Expand viewCollapse view
$ ifconfig -a

enp0s3    Link encap:Ethernet  HWaddr 08:00:27:20:cc:68 
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:47696 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21599 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:63548402 (63.5 MB)  TX bytes:1574417 (1.5 MB)

enp0s8    Link encap:Ethernet  HWaddr 08:00:27:55:df:60 
          inet addr:172.16.0.101  Bcast:172.31.255.255  Mask:255.240.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:405 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4334 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:52390 (52.3 KB)  TX bytes:418685 (418.6 KB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:760 errors:0 dropped:0 overruns:0 frame:0
          TX packets:760 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:60930 (60.9 KB)  TX bytes:60930 (60.9 KB)


$ route -n
[pre]Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.0.2.2        0.0.0.0         UG    100    0        0 enp0s3
10.0.2.0        0.0.0.0         255.255.255.0   U     100    0        0 enp0s3
172.16.0.0      0.0.0.0         255.240.0.0     U     100    0        0 enp0s8[/pre]


$ ping 172.16.0.1
PING 172.16.0.1 (172.16.0.1) 56(84) bytes of data.
64 bytes from 172.16.0.1: icmp_seq=1 ttl=128 time=7.37 ms
64 bytes from 172.16.0.1: icmp_seq=2 ttl=128 time=0.719 ms
64 bytes from 172.16.0.1: icmp_seq=3 ttl=128 time=0.767 ms
64 bytes from 172.16.0.1: icmp_seq=4 ttl=128 time=0.453 ms
64 bytes from 172.16.0.1: icmp_seq=5 ttl=128 time=1.02 ms
^C
--- 172.16.0.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4078ms
rtt min/avg/max/mdev = 0.453/2.067/7.370/2.657 ms
Stradman
 
Posts: 18
Joined: 16. Aug 2019, 11:51

Re: Host-only network stops working, when connecting to specific cable

Postby fth0 » 19. Aug 2019, 18:55

Thank you for the provided information.

Before I ask some questions that arose, a general advice regarding systematic testing: Since you (seem to) have a problem that is difficult to analyze, it may be important to restart the host system after each change regarding networking (e.g. VirtualBox network settings, network cabling), to prevent previous knowledge of the host to interfere with the next test. I know that it is tedious, but I've learned that often enough in the past. ;)

  1. Regarding enp0s3: In one of your previous posts you told us that the host-only adapter is the only enabled network adapter, but your guest shows an additional enp0s3 interface, probably connected to a NAT adapter. To which physical network interface was this adapter connected during your tests? Does your problem occur when this adapter is disabled?
  2. Regarding enp0s8: This interface seems to be connected to your host-only adapter, and has sent and received some network packets. Which protocols did work, especially when the ICMP protocol did not?
  3. Regarding the pings from guest to host (1): After pinging from host to guest, the host knows the MAC address for the guest IP address 172.16.0.101 and keeps it in its ARP cache for some time. Did you ping from guest to host shortly afterwards?
  4. Regarding the pings from guest to host (2): If you use Wireshark on the host to capture on all network interfaces simultaneously, and additionally capture in VirtualBox with the nictrace option on all VirtualBox network interfaces simultaneously, which network traffic do you see related to the failing ICMP echo request/reply pair (ARP, ICMP)?
  5. Regarding ping 10.0.0.1: Looks ok to me. The network is not in the routing table, so the ping goes to the default route (default gateway). If the default gateway routes to the 10.0.0.0/8 network, it maybe also does proxy ARP, which means that it maybe answers ARP requests to 10.69.69.x addresses. You could check the ARP and DHCP traffic on all network interfaces on the host to learn about the provided next hop (secondary) networks.
  6. Regarding the 'wild' RD network: In one of your previous posts you wrote '192.168.X.X/17', but Windows tells '255.255.224.0'. Small inaccuracy on your side, or is the provided network really 'wild'? :)
  7. Regarding the VM: Can you provide the VBox.log files for two complete runs of your VM (one with the Corp network, and one with RD network)? There is a lot of information in those files, including network statistics at the end.

Stradman wrote:It's the PCAPs that might contain unprotected sensitive data, hence not posting yet.

You're right, I wouldn't post PCAP files containing company data on a public forum either. :) If your company had a server where you could provide the files with restricted access to it, and if you additionally would trust me to keep secrets, and if the company would allow it, there would be a way. But those are a lot of ifs. ;)

EDIT: Added item 7 above.
Last edited by fth0 on 19. Aug 2019, 21:15, edited 1 time in total.
fth0
 
Posts: 142
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, macOS, ...

Re: Host-only network stops working, when connecting to specific cable

Postby scottgus1 » 19. Aug 2019, 19:06

I haven't had a chance to glance through this data myself yet, but I did notice this so far:
Stradman wrote:CORP NETWORK

HOST
=====================================================================
>ipconfig /all

.....
IPv4 Address. . . . . . . . . . . : 134.37.124.236(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
....
Default Gateway . . . . . . . . . : 134.37.124.1
DHCP Server . . . . . . . . . . . : 134.37.4.4
DNS Servers . . . . . . . . . . . : 134.37.1.53

Isn't 134.anything an internet address? I didn't see it in the various googlings I did on what the private IP addresses should be. Network gurus, does this ip range for a supposedly NATted company network seem OK?
Human government is like that crazy uncle who hides a quarter in his fist behind his back, then asks you to guess which fist the quarter is in...
No matter which side you choose, Left or Right, both Sides are empty.
scottgus1
 
Posts: 4262
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Win7

Re: Host-only network stops working, when connecting to specific cable

Postby fth0 » 19. Aug 2019, 20:19

@scottgus1:
Yes, these are public IP addresses. A company network does not have to use private IP addresses, and it does not have to be NATted. It can be simply routed to/from the Internet using its own public IP addresses.

PS: Better don't ask questions regarding these specific IP addresses in this public forum (for privacy reasons), or the OP may not talk to us any more. ;)
fth0
 
Posts: 142
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, macOS, ...

Re: Host-only network stops working, when connecting to specific cable

Postby Stradman » 20. Aug 2019, 08:44

fth0 wrote:
  1. Regarding enp0s3: In one of your previous posts you told us that the host-only adapter is the only enabled network adapter, but your guest shows an additional enp0s3 interface, probably connected to a NAT adapter. To which physical network interface was this adapter connected during your tests? Does your problem occur when this adapter is disabled?
  2. Regarding enp0s8: This interface seems to be connected to your host-only adapter, and has sent and received some network packets. Which protocols did work, especially when the ICMP protocol did not?
  3. Regarding the pings from guest to host (1): After pinging from host to guest, the host knows the MAC address for the guest IP address 172.16.0.101 and keeps it in its ARP cache for some time. Did you ping from guest to host shortly afterwards?
  4. Regarding the pings from guest to host (2): If you use Wireshark on the host to capture on all network interfaces simultaneously, and additionally capture in VirtualBox with the nictrace option on all VirtualBox network interfaces simultaneously, which network traffic do you see related to the failing ICMP echo request/reply pair (ARP, ICMP)?
  5. Regarding ping 10.0.0.1: Looks ok to me. The network is not in the routing table, so the ping goes to the default route (default gateway). If the default gateway routes to the 10.0.0.0/8 network, it maybe also does proxy ARP, which means that it maybe answers ARP requests to 10.69.69.x addresses. You could check the ARP and DHCP traffic on all network interfaces on the host to learn about the provided next hop (secondary) networks.
  6. Regarding the 'wild' RD network: In one of your previous posts you wrote '192.168.X.X/17', but Windows tells '255.255.224.0'. Small inaccuracy on your side, or is the provided network really 'wild'? :)
  7. Regarding the VM: Can you provide the VBox.log files for two complete runs of your VM (one with the Corp network, and one with RD network)? There is a lot of information in those files, including network statistics at the end.



  1. It is connected to the only physical port I am on. using the NATed interface enp0s3 has no effect here.
  2. From Guest -> Host, no protocols above link level (2) work, so from IP-level up it's dead. (Only ARP is seen working after connecting to the RD cable)
  3. I've been trying this in different ways. By dropping the ARP caches simultaneously and one by one.
  4. I saw only ICMP requests and APR reguest/reply. On the last captures I did simultaneously on HOST+GUEST on the host-only adapter, I saw only one copy of the ARP request/reply pair, on one side only. But not sure if this really is a factor here. At least the pointed MAC-addresses mathced & correct.
  5. Yes, 10.0.0.0 network might reside under the router, not on the same link/switch, so that is correct. (It's all coming back to me after 10 years, how to debug the network stuff, except small-scale home nets..)
  6. Oops, meant /19, but anyways a smaller block than the Host-only network is by default (/16?, IIRC...)
  7. You mean. boot up, ping, shutdown?
Stradman
 
Posts: 18
Joined: 16. Aug 2019, 11:51

Re: Host-only network stops working, when connecting to specific cable

Postby fth0 » 20. Aug 2019, 11:40

Stradman wrote:
fth0 wrote:Regarding the VM: Can you provide the VBox.log files for two complete runs of your VM (one with the Corp network, and one with RD network)? There is a lot of information in those files, including network statistics at the end.

You mean. boot up, ping, shutdown?

Yes, and also boot the host before each run, if possible.
fth0
 
Posts: 142
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, macOS, ...

Re: Host-only network stops working, when connecting to specific cable

Postby Stradman » 20. Aug 2019, 12:04

Attached.
Attachments
vboxlogs_ping_in_rd_and_corp.zip
Guest->Host ping logs, Corp & RD net
(68.94 KiB) Downloaded 3 times
Last edited by socratis on 20. Aug 2019, 12:09, edited 1 time in total.
Reason: Removed unnecessary verbatim quote of the whole previous message.
Stradman
 
Posts: 18
Joined: 16. Aug 2019, 11:51

Re: Host-only network stops working, when connecting to specific cable

Postby Stradman » 21. Aug 2019, 13:26

Ok, down to business.

I configured a home box router with similar kind of IP-network configuration that our RD-network has. And the router also serves DHCP addresses from the same address space.

Configuration:
Net: 192.168.96.0
Subnet Mask: 255.255.224.0
Default Gateway: 192.168.100.1

Host-Only network adapter:
IPv4 Address. . . . . . . . . . . : 172.16.0.1
Subnet Mask . . . . . . . . . . . : 255.240.0.0

Right after connecting to this box the ping stops, in the exact way as with our RD-network. So I highy regard this as a bug in VirtualBox, unless properly documented and proven working.

To me, Host-only networking is *not* working in host connection with private IP-address space 192.168.X.X.

(Let me hypothesize: a hard-coded assumption of IP-address space in the code..?)

EDIT: https://www.virtualbox.org/ticket/18857

EDIT2: Any 192.168.*.* IP-network for host cable connection will do to reproudce this, apparently... now verified with the default config of the router, 192.168.1.0 / 24.
Last edited by Stradman on 22. Aug 2019, 11:51, edited 2 times in total.
Stradman
 
Posts: 18
Joined: 16. Aug 2019, 11:51

Re: Host-only network stops working, when connecting to 192.168.X.X IP-network

Postby scottgus1 » 21. Aug 2019, 19:50

I just updated my Windows 10 host Virtualbox & extension pack to 6.0.10. I have a house network of 192.168.0.### net mask 255.255.255.0. I set two of my guests to host-only on the default 192.168.56.### range.

My host-only network:
Host 192.168.56.1
guest XP 192.168.56.101 (by host-only DHCP)
guest W7 192.168.56.102 (by host-only DHCP)

Note that I cannot ping 192.168.0.anything from in the guests, as I would expect.
I can reach the host Windows 10 shared folders from within the Windows 7 guest by accessing \\192.168.56.1

I can ping between host and guests all six directions without limit using 192.168.56.destination#.

My host is actively plugged into a normal 192.168 network (normal in the sense that the net mask restricts to only changing the last set of numbers, usual house router defaults).

Without changing my house router to an exact copy of the RD network settings yet, I would at least say that as to:
Stradman wrote:EDIT2: Any 192.168.*.* IP-network for host cable connection will do to reproudce this

I see a hand or a foot sticking out from under that blanket. :lol:

There may in fact be a problem in Virtualbox - glitches & bugs do happen. But 6.0.10 has been out for a few blocks of time and this kind of problem hasn't been shown to be a really wide-ranging issue that rather a geeky level of perusing the Virtualbox forums has been able to let me see yet. If host-only failed on a 192.168 netowrk unioiversally, Id' think it would have been noticed more, seeing as 192.168 is soewhat ubiquitous. I would lean more to a unique setup at your office that has also influenced your host.

Do you have a reasonable home PC you could try Virtualbox & host-only on with your guests (see Moving a VM), just using the default usual house router defaults?
Last edited by scottgus1 on 21. Aug 2019, 20:56, edited 1 time in total.
Human government is like that crazy uncle who hides a quarter in his fist behind his back, then asks you to guess which fist the quarter is in...
No matter which side you choose, Left or Right, both Sides are empty.
scottgus1
 
Posts: 4262
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Win7

Re: Host-only network stops working, when connecting to 192.168.X.X IP-network

Postby scottgus1 » 21. Aug 2019, 20:25

Turns out aI have an old router I might be able to try this on. Stradman, I see you set your test router to
Net: 192.168.100.0
Subnet Mask: 255.255.224.0
Default Gateway: 192.168.100.1

The subnet mask allows a change of 31 numbers in the third set. Seemingly from 100 to 130 or 131 I guess.

However, in your RD host info above, while your default gateway is 192.168.100.1, the route table network destination seems to go from 192.168.96.0 to 192.168.127.255, also a third-number spread of 31.

The corp ip route table network destination starts at .0 and ends at .255 on the last number, no change in any others, consistent with the subnet mask 255.255.255.0 allowing only changes in the last number.

You don't suppose that your RD network is actually starting at .96? I would want to test exactly if I get a chance.
Human government is like that crazy uncle who hides a quarter in his fist behind his back, then asks you to guess which fist the quarter is in...
No matter which side you choose, Left or Right, both Sides are empty.
scottgus1
 
Posts: 4262
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Win7

Re: Host-only network stops working, when connecting to 192.168.X.X IP-network

Postby Stradman » 21. Aug 2019, 21:09

I would lean more to a unique setup at your office that has also influenced your host.

I also did try the separate router default setting: 192.168.1.0 / 24 for the Ethernet cable connection, to try to rule out an RD-network mishap.

Do you have a reasonable home PC you could try Virtualbox & host-only on with your guests (see Moving a VM), just using the default usual house router defaults?

I don't have a home setup with Windows 10 (gladly). With openSUSE-host / Ubuntu 18.04 Guest I have no issues here, with rather standard 192.168.0.0 network. I guess I could try with my corp laptop, just for the fun of it..

I just updated my Windows 10 host Virtualbox & extension pack to 6.0.10. I have a house network of 192.168.0.### net mask 255.255.255.0. I set two of my guests to host-only on the default 192.168.56.### range.

My host-only network:
Host 192.168.56.1
guest XP 192.168.56.101 (by host-only DHCP)
guest W7 192.168.56.102 (by host-only DHCP)

Ok. Note still that I am using Ubuntu 18.04 Guest. Not sure if that is key factor here..

scottgus1 wrote:Turns out aI have an old router I might be able to try this on. Stradman, I see you set your test router to
Net: 192.168.100.0
Subnet Mask: 255.255.224.0
Default Gateway: 192.168.100.1

The subnet mask allows a change of 31 numbers in the third set. Seemingly from 100 to 130 or 131 I guess.

However, in your RD host info above, while your default gateway is 192.168.100.1, the route table network destination seems to go from 192.168.96.0 to 192.168.127.255, also a third-number spread of 31.

The corp ip route table network destination starts at .0 and ends at .255 on the last number, no change in any others, consistent with the subnet mask 255.255.255.0 allowing only changes in the last number.
You don't suppose that your RD network is actually starting at .96? I would want to test exactly if I get a chance.


Indeed, it is .240.0 mask, so it should be the lower 192.168.96.0 ... 192.168.127.255.
My hasty copy-paste -error here.. But, still I am not even attempting to access any outside network addresses (even with the faulty network address 192.168.100.*) by pinging, but only up to the Host-Only "outer" IP: 172.16.0.1. It would a bit odd that the .100. could be a factor here, as there would be no routing happening to the 192.168.*.* network. (And the delivery is done link-local in any case, regardless of cable connected or not, as we can see the ARP-queries for 172.16.0.1)

The only ping access would be in 171.16.0.0 address block. And: disconnecting the network cable makes this work, so at least in that case there is no routing done to 192.168.*.*.

Also, as mentioned earlier, I was able to ping across to/from another Guest OS (Ubuntu 18.04) in the Host-only network. But again, the problem is that I cannot ping the "outside" Host-Only interface. So Guests can communicate between each other, but not over to the Host Windows side, 172.16.0.1.


EDIT:

However, in your RD host info above, while your default gateway is 192.168.100.1, the route table network destination seems to go from 192.168.96.0 to 192.168.127.255, also a third-number spread of 31.

Fixed in the original message
Stradman
 
Posts: 18
Joined: 16. Aug 2019, 11:51

PreviousNext

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: Google [Bot] and 21 guests