Hostonly network bad route after windows resumes from sleep

Discussions related to using VirtualBox on Windows hosts.
Post Reply
praveen12bnitt
Posts: 3
Joined: 11. Aug 2015, 23:03

Hostonly network bad route after windows resumes from sleep

Post by praveen12bnitt »

The linux guest OS has 2 network adapters. The first one is a NAT network and the second one is a hostonly network

The hostonly network has the below configuration
IP v4 address : 192.168.99.1
IP v4 network mask : 255.255.255.0
DHCP Server enabled.
DHCP Server address : 192.168.99.1
DHCP Server mask : 255.255.255.0
Lower Address Bound : 192.168.99.100
Upper Address Bonnd : 192.168.99.254

I start the linux vm and do if config, i can see that the guest os received a IP address of 192.168.99.100. Screenshot of ifconfig attached.

Now i come to the host os and run ROUTE PRINT

Code: Select all

===========================================================================
Interface List
 14...80 00 0b 39 68 49 ......Bluetooth Device (Personal Area Network)
 12...80 00 0b 39 68 45 ......Intel(R) Centrino(R) Advanced-N 6235
 11...ec f4 bb 6b 25 da ......Intel(R) Ethernet Connection I217-LM
 23...0a 00 27 00 00 00 ......VirtualBox Host-Only Ethernet Adapter
  1...........................Software Loopback Interface 1
 17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
 15...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
 21...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #7
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    192.168.1.254     192.168.1.67     25
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      192.168.1.0    255.255.255.0         On-link      192.168.1.67    281
     192.168.1.67  255.255.255.255         On-link      192.168.1.67    281
    192.168.1.255  255.255.255.255         On-link      192.168.1.67    281
     192.168.99.0    255.255.255.0         On-link      192.168.99.1    266
     192.168.99.1  255.255.255.255         On-link      192.168.99.1    266
   192.168.99.255  255.255.255.255         On-link      192.168.99.1    266
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link      192.168.99.1    266
        224.0.0.0        240.0.0.0         On-link      192.168.1.67    281
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link      192.168.99.1    266
  255.255.255.255  255.255.255.255         On-link      192.168.1.67    281
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
 12    281 ::/0                     fe80::bae6:25ff:fe5e:b3c9
  1    306 ::1/128                  On-link
 12     33 2602:306:8b1b:4290::/64  On-link
 12    281 2602:306:8b1b:4290:3ca6:81b:9705:7404/128
                                    On-link
 12    281 2602:306:8b1b:4290:a503:ae30:1a7f:56ab/128
                                    On-link
 12    281 fe80::/64                On-link
 23    266 fe80::/64                On-link
 12    281 fe80::a503:ae30:1a7f:56ab/128
                                    On-link
 23    266 fe80::f97b:f9a5:e92f:7359/128
                                    On-link
  1    306 ff00::/8                 On-link
 23    266 ff00::/8                 On-link
 12    281 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None
If i run "ping 192.168.99.100", everything works.

Code: Select all

> ping 192.168.99.100

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

I now hibernate my host (running windows 7) and resume it form hibernate.
Now when i run ROUTE PRINT, 192.168.99.x entries are missing.

Code: Select all

> route print
===========================================================================
Interface List
 14...80 00 0b 39 68 49 ......Bluetooth Device (Personal Area Network)
 12...80 00 0b 39 68 45 ......Intel(R) Centrino(R) Advanced-N 6235
 11...ec f4 bb 6b 25 da ......Intel(R) Ethernet Connection I217-LM
 23...0a 00 27 00 00 00 ......VirtualBox Host-Only Ethernet Adapter
  1...........................Software Loopback Interface 1
 19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
 15...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
 21...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #7
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    192.168.1.254     192.168.1.67     25
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      169.254.0.0      255.255.0.0         On-link    169.254.115.89    266
   169.254.115.89  255.255.255.255         On-link    169.254.115.89    266
  169.254.255.255  255.255.255.255         On-link    169.254.115.89    266
      192.168.1.0    255.255.255.0         On-link      192.168.1.67    281
     192.168.1.67  255.255.255.255         On-link      192.168.1.67    281
    192.168.1.255  255.255.255.255         On-link      192.168.1.67    281
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link    169.254.115.89    266
        224.0.0.0        240.0.0.0         On-link      192.168.1.67    281
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link    169.254.115.89    266
  255.255.255.255  255.255.255.255         On-link      192.168.1.67    281
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
 12    281 ::/0                     fe80::bae6:25ff:fe5e:b3c9
  1    306 ::1/128                  On-link
 12     33 2602:306:8b1b:4290::/64  On-link
 12    281 2602:306:8b1b:4290:3ca6:81b:9705:7404/128
                                    On-link
 12    281 2602:306:8b1b:4290:a503:ae30:1a7f:56ab/128
                                    On-link
 12    281 fe80::/64                On-link
 23    266 fe80::/64                On-link
 12    281 fe80::a503:ae30:1a7f:56ab/128
                                    On-link
 23    266 fe80::f97b:f9a5:e92f:7359/128
                                    On-link
  1    306 ff00::/8                 On-link
 23    266 ff00::/8                 On-link
 12    281 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None
If i start my linux guest vm , it starts, but i am unable to ping 192.168.99.100 ip address. I get the below error.

Code: Select all

> ping 192.168.99.100

Pinging 192.168.99.100 with 32 bytes of data:
Request timed out.
Has anyone encountered this error?
Top
praveen12bnitt
Posts: 3
Joined: 11. Aug 2015, 23:03

Re: Hostonly network bad route after windows resumes from sl

Post by praveen12bnitt »

If i do a full restart of my windows 7 machine, everything starts working again. So the problem when windows resumes from sleep or hibernate.
Top
DiFm
Posts: 5
Joined: 12. Aug 2015, 09:54

Re: Hostonly network bad route after windows resumes from sl

Post by DiFm »

I can confirm this. I have the same problem i created a this topic recently "Host-only-adapter not working no connection to host". Restarting windows 7 fixes the problem. I guess this is a bug.
Top
Post Reply

Return to “VirtualBox on Windows Hosts”