virtualbox.org

End user forums for VirtualBox
https://forums.virtualbox.org/

Win XP SP3 - bridged network - valid IP but no internet

https://forums.virtualbox.org/viewtopic.php?t=75079

Page 1 of 1

Win XP SP3 - bridged network - valid IP but no internet

Posted: 9. Dec 2015, 15:50
by nomadictribe
Hi,

I've just completed a sandboxed enviroment where the WinXP guest resides inside of another virtualbox guest (debian) which funtions as the host system.
The problem is that the WinXP guest inside the virtualhost aquires an IP address via dhcp but has no internet access. I can ping the local IP of the virtualhost(debian) but thats it.
The guest has no access to the LAN (can't ping the gateway or dhcp server) or to the internet and I can't figure out why.
I tried installing debian inside the virtualhost(debina) just to check whether or not it would get connectivity and it doesm so it's not the virtualhost part thats the problem it's something
in connection with the WinXP guest. Does anyone have any idea why that phenomenon should occur?

Best regards

nomadictribe

Re: Win XP SP3 - bridged network - valid IP but no internet

Posted: 9. Dec 2015, 16:05
by loukingjr
VirtualBox doesn't support nesting hypervisors. Could be one reason.

Re: Win XP SP3 - bridged network - valid IP but no internet

Posted: 9. Dec 2015, 17:24
by nomadictribe
Yeah I thought about that too but then the problem should be replicable with for example a debian guest instead of the windows guest.
Well I tried that already, to no avail the installed debian guest had network accesss.

Re: Win XP SP3 - bridged network - valid IP but no internet

Posted: 9. Dec 2015, 19:32
by socratis
Would you mind sharing some of the details of your network setup? Wireless, wired, private, public, anything you can think of. One thing though; please do not try to obfuscate the details (like 10.x.x.x) because we're going to have to guess, and that doesn't help.

A good idea would be to post the output of your "ipconfig /all" (from WinXP) and "ifconfig -a" (from Debian) as well as from your actual host (I couldn't figure out from your post what it was). We'll need IPs, gateways, masks, DHCP, DNS servers for all of them.

Just because it's not supported, it doesn't mean it won't work. I've done it. But do not expect anything either rock-solid, or a performance monster.

Re: Win XP SP3 - bridged network - valid IP but no internet

Posted: 10. Dec 2015, 15:12
by nomadictribe
ok here we go.

The physical host (Windows 10)

Code: Select all

# ipconfig /all
Windows-IP-Konfiguration

   Hostname  . . . . . . . . . . . . : DESKTOP-C4U813I
   Primäres DNS-Suffix . . . . . . . :
   Knotentyp . . . . . . . . . . . . : Hybrid
   IP-Routing aktiviert  . . . . . . : Nein
   WINS-Proxy aktiviert  . . . . . . : Nein
   DNS-Suffixsuchliste . . . . . . . : LAN1.de

Drahtlos-LAN-Adapter WiFi:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Dell Wireless 1550 802.11ac
   Physische Adresse . . . . . . . . : 40-F0-2F-ED-F3-97
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter LAN-Verbindung* 1:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physische Adresse . . . . . . . . : 42-F0-2F-ED-F3-97
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Ethernet-Adapter Ethernet:

   Verbindungsspezifisches DNS-Suffix: 
   Beschreibung. . . . . . . . . . . : Intel(R) Ethernet Connection I217-LM
   Physische Adresse . . . . . . . . : EC-F4-BB-13-BA-2C
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : fe80::e580:eb20:1865:9c97%22(Bevorzugt)
   IPv4-Adresse  . . . . . . . . . . : 172.16.31.111(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Lease erhalten. . . . . . . . . . : Donnerstag, 10. Dezember 2015 08:24:37
   Lease läuft ab. . . . . . . . . . : Freitag, 18. Dezember 2015 13:01:49
   Standardgateway . . . . . . . . . : 172.16.31.250
   DHCP-Server . . . . . . . . . . . : 172.16.31.4
   DHCPv6-IAID . . . . . . . . . . . : 166524091
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-1D-C7-CB-73-EC-F4-BB-13-BA-2C
   DNS-Server  . . . . . . . . . . . : 172.16.31.4
   NetBIOS über TCP/IP . . . . . . . : Aktiviert

Ethernet-Adapter VirtualBox Host-Only Network:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
   Physische Adresse . . . . . . . . : 0A-00-27-00-00-00
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : fe80::d473:a80a:a72d:8b5a%5(Bevorzugt)
   IPv4-Adresse  . . . . . . . . . . : 192.168.56.1(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Standardgateway . . . . . . . . . :
   DHCPv6-IAID . . . . . . . . . . . : 336199719
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-1D-C7-CB-73-EC-F4-BB-13-BA-2C
   DNS-Server  . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS über TCP/IP . . . . . . . : Aktiviert

Tunneladapter LAN-Verbindung* 3:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter isatap.{39F0801E-72BD-4BB1-B853-C808706F11E7}:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter isatap.LAN1.de:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix: 
   Beschreibung. . . . . . . . . . . : Microsoft ISATAP Adapter #4
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

# route PRINT
===========================================================================
Schnittstellenliste
 21...40 f0 2f ed f3 97 ......Dell Wireless 1550 802.11ac
 14...42 f0 2f ed f3 97 ......Microsoft Wi-Fi Direct Virtual Adapter
 22...ec f4 bb 13 ba 2c ......Intel(R) Ethernet Connection I217-LM
  5...0a 00 27 00 00 00 ......VirtualBox Host-Only Ethernet Adapter
  1...........................Software Loopback Interface 1
  8...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
 18...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
  6...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4
===========================================================================

IPv4-Routentabelle
===========================================================================
Aktive Routen:
     Netzwerkziel    Netzwerkmaske          Gateway    Schnittstelle Metrik
          0.0.0.0          0.0.0.0    172.16.31.250    172.16.31.111     10
        127.0.0.0        255.0.0.0   Auf Verbindung         127.0.0.1    306
        127.0.0.1  255.255.255.255   Auf Verbindung         127.0.0.1    306
  127.255.255.255  255.255.255.255   Auf Verbindung         127.0.0.1    306
      172.16.31.0    255.255.255.0   Auf Verbindung     172.16.31.111    266
    172.16.31.111  255.255.255.255   Auf Verbindung     172.16.31.111    266
    172.16.31.255  255.255.255.255   Auf Verbindung     172.16.31.111    266
     192.168.56.0    255.255.255.0   Auf Verbindung      192.168.56.1    266
     192.168.56.1  255.255.255.255   Auf Verbindung      192.168.56.1    266
   192.168.56.255  255.255.255.255   Auf Verbindung      192.168.56.1    266
        224.0.0.0        240.0.0.0   Auf Verbindung         127.0.0.1    306
        224.0.0.0        240.0.0.0   Auf Verbindung      192.168.56.1    266
        224.0.0.0        240.0.0.0   Auf Verbindung     172.16.31.111    266
  255.255.255.255  255.255.255.255   Auf Verbindung         127.0.0.1    306
  255.255.255.255  255.255.255.255   Auf Verbindung      192.168.56.1    266
  255.255.255.255  255.255.255.255   Auf Verbindung     172.16.31.111    266
===========================================================================
Ständige Routen:
  Keine

IPv6-Routentabelle
===========================================================================
Aktive Routen:
 If Metrik Netzwerkziel             Gateway
  1    306 ::1/128                  Auf Verbindung
  5    266 fe80::/64                Auf Verbindung
 22    266 fe80::/64                Auf Verbindung
  5    266 fe80::d473:a80a:a72d:8b5a/128
                                    Auf Verbindung
 22    266 fe80::e580:eb20:1865:9c97/128
                                    Auf Verbindung
  1    306 ff00::/8                 Auf Verbindung
  5    266 ff00::/8                 Auf Verbindung
 22    266 ff00::/8                 Auf Verbindung
===========================================================================
Ständige Routen:
  Keine
The virtualhost (Debian 8)

Code: Select all

# ifconfig -a
eth0      Link encap:Ethernet  Hardware Adresse 08:00:27:e9:94:59  
          inet Adresse:172.16.31.102  Bcast:172.16.31.255  Maske:255.255.255.0
          inet6-Adresse: fe80::a00:27ff:fee9:9459/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX packets:893 errors:0 dropped:0 overruns:0 frame:0
          TX packets:101 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000 
          RX bytes:182188 (177.9 KiB)  TX bytes:13121 (12.8 KiB)

lo        Link encap:Lokale Schleife  
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:65536  Metrik:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0 
          RX bytes:1344 (1.3 KiB)  TX bytes:1344 (1.3 KiB)

# route
route
Kernel-IP-Routentabelle
Ziel            Router          Genmask         Flags Metric Ref    Use Iface
default         172.16.31.250   0.0.0.0         UG    1024   0        0 eth0
link-local      *               255.255.0.0     U     1000   0        0 eth0
172.16.31.0     *               255.255.255.0   U     0      0        0 eth0
The virtual guest (Win XP SP3)

Code: Select all

# ipconfig -all

Windows-IP-Konfiguration

        Hostname. . . . . . . . . . . . . : testbed-027e3b7
        Primäres DNS-Suffix . . . . . . . :
        Knotentyp . . . . . . . . . . . . : Unbekannt
        IP-Routing aktiviert. . . . . . . : Nein
        WINS-Proxy aktiviert. . . . . . . : Nein
        DNS-Suffixsuchliste . . . . . . . : LAN1.de

Ethernetadapter LAN-Verbindung:

        Verbindungsspezifisches DNS-Suffix: LAN1.de
        Beschreibung. . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter

        Physikalische Adresse . . . . . . : 08-00-27-22-2C-B5
        DHCP aktiviert. . . . . . . . . . : Ja
        Autokonfiguration aktiviert . . . : Ja
        IP-Adresse. . . . . . . . . . . . : 172.16.31.107
        Subnetzmaske. . . . . . . . . . . : 255.255.255.0
        Standardgateway . . . . . . . . . : 172.16.31.250
        DHCP-Server . . . . . . . . . . . : 172.16.31.4
        DNS-Server. . . . . . . . . . . . : 172.16.31.4
        Lease erhalten. . . . . . . . . . : Donnerstag, 10. Dezember 2015 14:06:
29
        Lease läuft ab. . . . . . . . . . : Freitag, 18. Dezember 2015 14:06:29

# route PRINT
===========================================================================
Schnittstellenliste
0x1 ........................... MS TCP Loopback interface
0x2 ...08 00 27 22 2c b5 ...... Intel(R) PRO/1000 MT Desktop Adapter - Paketplan
er-Miniport
===========================================================================
===========================================================================
Aktive Routen:
     Netzwerkziel    Netzwerkmaske          Gateway   Schnittstelle  Anzahl
          0.0.0.0          0.0.0.0    172.16.31.250   172.16.31.107       10
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      172.16.31.0    255.255.255.0    172.16.31.107   172.16.31.107       10
    172.16.31.107  255.255.255.255        127.0.0.1       127.0.0.1       10
   172.16.255.255  255.255.255.255    172.16.31.107   172.16.31.107       10
        224.0.0.0        240.0.0.0    172.16.31.107   172.16.31.107       10
  255.255.255.255  255.255.255.255    172.16.31.107   172.16.31.107       1
Standardgateway:     172.16.31.250
===========================================================================
Ständige Routen:
  Keine
Thats about it. If you need anything more just say the word.

Re: Win XP SP3 - bridged network - valid IP but no internet

Posted: 12. Dec 2015, 21:59
by socratis
Can I take a wild guess here and assume that you're using wireless? Because I tried your setup, and here's what I found:
- Using wireless, the 2nd VM would get a valid IP, but couldn't do anything more. Zilch.
- Using wired, the 2nd VM would get a valid IP and would act normally on the network. Completely.

Tried it with several combinations of hostVM, guestVM, and in all the cases the results were the same. So, could you please wire your host and then bridge your hostVM and then bridge your guestVM and see if it works?

Re: Win XP SP3 - bridged network - valid IP but no internet

Posted: 15. Dec 2015, 15:38
by nomadictribe
The host is wired since wifi is permanently disbled in this rig.
I too tried a few things and usually the nested guest (mostly linux tests) gets an ip address, only the winXP guest wont.
Well linux as nested guest doesn't work since the whole setup is for vm introspection and needs a windows as the nested guest.
I'm gonna try another host system maybe my current does something nonstandard.

Re: Win XP SP3 - bridged network - valid IP but no internet

Posted: 15. Dec 2015, 15:51
by socratis
I'll try it and see what it comes back with...


<OffTopic>
nomadictribe wrote:the whole setup is for vm introspection
I didn't recognize that word, so I looked it up. Somehow I have a feeling that this is not what you meant :)
Wikipedia wrote:Introspection is the examination of one's own conscious thoughts and feelings. In psychology the process of introspection relies exclusively on observation of one's mental state, while in a spiritual context it may refer to the examination of one's soul.
</OffTopic>

Re: Win XP SP3 - bridged network - valid IP but no internet

Posted: 15. Dec 2015, 16:19
by nomadictribe
FYI 31C3 talk on vm introspection https://www.youtube.com/watch?v=ElggombHA8E
All times are UTC+02:00
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited