virtualbox.org

Greetings to all of you.

I'm currently getting started using VirtualBox instead of VMware and im stumbling on bridged networks on guests.

My setup is as follows...
- Host with windows 10 connected to a DHCP-capable copper network (cable not wifi, internet working)
- Guest with winows 7 (fresh install) which I want to integrate into that network using a bridge.
- Guest OS hat guest-extensions installed.

According to the tutorials I found it should be as simple as configuring the bridge in that guest-machine settings.
Attached you can see a sceenshot of my host maschine network adapters an guest-configuration.

: Adapter.png (104.69 KiB) Viewed 3728 times

Now... the guest-OS gets an IP assigned from the Router (192.168.1.1) as you can see in the second attachment.

: Guest recieves IP from network; GuesOS_IP_from_DHCP.png (36.69 KiB) Viewed 3728 times

However, I don't get internet access on the guest. Even though the guest received an IP from the router it cannot ping the router/gateway (only the host can).
The only IP the guest-OS can ping is the IP of the host.

: Guest ping; Guest_PINK.png (80.59 KiB) Viewed 3728 times

Windows firewall is deactivated on host an guest.

I tried all sorts of things I found in tutorials und threads here but I couldn't get it to work. Has anyoone got somthing.
Thanks, with regrads... Heinz.

Can other machines on your LAN ping the gateway? Not all devices respond to pings.

But, if you can ping "8.8.8.8" (Google DNS), then the gateway and bridge feature are working.

You also seem to have DHCP and a private DNS on two separate networks - is that intended? (192.168.1.x and 192.168.0.x, netmask only allows low 8 bits for device address).

Hello mpack.

Router/Gateway 192.168.1.1 and also Google-DNS 8.8.8.8 can be pinged by everyone on the network including the host maschine.

Only the guest cannot ping anything alse than the host. The guest got 192.168.1.164 from the DHCP but can only ping 192.168.1.162 (the host) but nothing further.

I also tried a different network (192.168.8.x) with just an SIM-card-router and only the host-maschine with its guest. Same result (all cabled no wifi). The guest Maschine got an IP from the SIM-card-router but couldn't ping it back or access the internet. Only the host itself can.

mpack wrote: You also seem to have DHCP and a private DNS on two separate networks - is that intended? (192.168.1.x and 192.168.0.x, netmask only allows low 8 bits for device address).

Yes that is how that network is structured. There is a main net 192.168.0.x/24 and a smaller net with 192.168.1.x/24. The main net has the DNS and DHCP.

But that doesn't seem to be the problem.
When I try it with a SIM-card router directly cabled to the host-machine, then there is only ony device/network for gateway and DNS/DHCP. Same result.

Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

mpack wrote:Please provide a VM log file.

Here you go...

I had a cursory sniff but can't see anything obvious apart from a missing audio-device which the host-pc doesn't have.

HeinzHB wrote:
mpack wrote: You also seem to have DHCP and a private DNS on two separate networks - is that intended? (192.168.1.x and 192.168.0.x, netmask only allows low 8 bits for device address).
Yes that is how that network is structured. There is a main net 192.168.0.x/24 and a smaller net with 192.168.1.x/24. The main net has the DNS and DHCP.

But that doesn't seem to be the problem.

I personally am not so sure about this, due to that 255.255.255.0 net mask. That mask forces the first three octets (192.168.1) to be unchangeable. 192.168.0 is a change in the third octet, which is blocked by the net mask. (At least that's how I have understood it.)

Seems to me this is a non-standard setup, and anything goes. Bridged works when the DNS is in the correct network range allowed by the net mask.

scottgus1 wrote:Seems to me this is a non-standard setup, and anything goes. Bridged works when the DNS is in the correct network range allowed by the net mask.

It is nothing that special, just a company network with multiple /24 subnets. The config is working for everyone in it. The DNS-Servers in the 0-subnet can be reached from the 1-subnet via the Gateway.

But maybe that wasn't the best example for the problem maybe, since it adds some unnecessary variables. Sorry.
To rule out any special configuration problems in that company net I disconnected the host machine from the company net and connected it to a SIM-card-router (LTE-internet-router) for testing.
Just the LTE-Router and the host-machine connected together with a cable. All in the same subnet where the LTE-Router does everything (Gateway, DHCP, DNS).

The result remains the same
- Host machine
- Receives IP from LTE-Router
- Can ping LTE-Router
- Gets internet connection

- Guest machine
- Receives IP from LTE-Router
- Can ping host-machine
- Cannot ping LTE-Router
- Gets no internet connection

I don't have screenshots of that configuration since I'm out of office for the day. I made a little schematic to show the configuration that I tested with the LTE-Router

: LTE-Router_Test.png (32.9 KiB) Viewed 3684 times

Please post an "ipconfig /all" and a "ping 8.8.8.8" from both the host and the VM OS's while using the LTE router.

scottgus1 wrote:Please post an "ipconfig /all" and a "ping 8.8.8.8" from both the host and the VM OS's while using the LTE router.

OK thanks so far, will post that when I'm back in the office tomorrow.

Good Morning to everybody!

Here are the ipconfig/all and ping 8.8.8.8 form the host an guest using only the LTE-Router.
Additional info if I switch the guest to NAT, it gets internet connection just fine.
Windows firewall is off in both machines.

Problem still as describe above, guest gets dynamic IP from LTE-Router but can then only ping the host without internet,

HOST IPCONFIG/ALL

HOST ipconfig/all wrote: Microsoft Windows [Version 10.0.17763.3287]
(c) 2018 Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\Bed>ipconfig /all

Windows-IP-Konfiguration

Hostname . . . . . . . . . . . . : DESKTOP-QJKI4LU
Primäres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Nein
DNS-Suffixsuchliste . . . . . . . : lan

Ethernet-Adapter LAN[X2 P1]:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Intel(R) EC1000R 1.0GbE Connection #2
Physische Adresse . . . . . . . . : D4-F5-27-EC-CB-4B
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja

Ethernet-Adapter LAN[X3 P1]:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Intel(R) EC1000S 1.0GbE Connection & Intel(R) EC2500S 2.5GbE Connection
Physische Adresse . . . . . . . . : D4-F5-27-EC-CB-4C
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja

Ethernet-Adapter VirtualBox Host-Only Network:

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physische Adresse . . . . . . . . : 0A-00-27-00-00-05
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::b883:8b458d69%5(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.116.1(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . :
DHCPv6-IAID . . . . . . . . . . . : 84541479
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-2A-9F-84-20-D4-F5-27-EC-CB-4A
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

Ethernet-Adapter LAN[X1 P1]:

Verbindungsspezifisches DNS-Suffix: lan
Beschreibung. . . . . . . . . . . : Intel(R) EC1000R 1.0GbE Connection
Physische Adresse . . . . . . . . : D4-F5-27-EC-CB-4A
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::45ad:b8f:4947:2675%2(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.8.199(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Lease erhalten. . . . . . . . . . : Mittwoch, 31. August 2022 07:38:40
Lease läuft ab. . . . . . . . . . : Mittwoch, 31. August 2022 19:38:40
Standardgateway . . . . . . . . . : 192.168.8.1
DHCP-Server . . . . . . . . . . . : 192.168.8.1
DHCPv6-IAID . . . . . . . . . . . : 47510823
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-2A-9F-84-20-D4-F5-27-EC-CB-4A
DNS-Server . . . . . . . . . . . : 192.168.8.1
NetBIOS über TCP/IP . . . . . . . : Aktiviert

HOST ping 8.8.8.8

HOST ping 8.8.8.8 wrote: C:\Users\Bed>ping 8.8.8.8

Ping wird ausgeführt für 8.8.8.8 mit 32 Bytes Daten:
Antwort von 8.8.8.8: Bytes=32 Zeit=28ms TTL=117
Antwort von 8.8.8.8: Bytes=32 Zeit=29ms TTL=117
Antwort von 8.8.8.8: Bytes=32 Zeit=30ms TTL=117
Antwort von 8.8.8.8: Bytes=32 Zeit=28ms TTL=117

Ping-Statistik für 8.8.8.8:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 28ms, Maximum = 30ms, Mittelwert = 28ms

GUEST ipconfig/all

GUEST ipconfig/all wrote: C:\Users\techniker>ipconfig /all

Windows-IP-Konfiguration

Hostname . . . . . . . . . . . . : testVMtechnik
Primäres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Nein
DNS-Suffixsuchliste . . . . . . . : lan

Ethernet-Adapter LAN-Verbindung:

Verbindungsspezifisches DNS-Suffix: lan
Beschreibung. . . . . . . . . . . : Intel(R) PRO/1000 MT-Desktopadapter
Physikalische Adresse . . . . . . : 08-00-27-8E-09-B1
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::e4ac:cb8a:bcc2:32b4%11(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.8.169(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Lease erhalten. . . . . . . . . . : Mittwoch, 31. August 2022 07:39:32
Lease läuft ab. . . . . . . . . . : Mittwoch, 31. August 2022 19:39:32
Standardgateway . . . . . . . . . : 192.168.8.1
DHCP-Server . . . . . . . . . . . : 192.168.8.1
DHCPv6-IAID . . . . . . . . . . . : 235405351
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-2A-9F-CC-F1-08-00-27-7A-7A-6E

DNS-Server . . . . . . . . . . . : 192.168.8.1
NetBIOS über TCP/IP . . . . . . . : Aktiviert

Tunneladapter isatap.lan:

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

GUEST ping
ping to 8.8.8.8
ping to 192.168.8.1 (LTE-Router)
ping to 192.168.8.199 (host machine)

GUEST ping wrote: C:\Users\techniker>ping 8.8.8.8

Ping wird ausgeführt für 8.8.8.8 mit 32 Bytes Daten:
Antwort von 192.168.8.169: Zielhost nicht erreichbar.
Antwort von 192.168.8.169: Zielhost nicht erreichbar.
Antwort von 192.168.8.169: Zielhost nicht erreichbar.
Antwort von 192.168.8.169: Zielhost nicht erreichbar.

Ping-Statistik für 8.8.8.8:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),

C:\Users\techniker>ping 192.168.8.1

Ping wird ausgeführt für 192.168.8.1 mit 32 Bytes Daten:
Antwort von 192.168.8.169: Zielhost nicht erreichbar.
Antwort von 192.168.8.169: Zielhost nicht erreichbar.
Antwort von 192.168.8.169: Zielhost nicht erreichbar.
Antwort von 192.168.8.169: Zielhost nicht erreichbar.

Ping-Statistik für 192.168.8.1:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),

C:\Users\techniker>ping 192.168.8.199

Ping wird ausgeführt für 192.168.8.199 mit 32 Bytes Daten:
Antwort von 192.168.8.199: Bytes=32 Zeit<1ms TTL=128
Antwort von 192.168.8.199: Bytes=32 Zeit<1ms TTL=128
Antwort von 192.168.8.199: Bytes=32 Zeit<1ms TTL=128
Antwort von 192.168.8.199: Bytes=32 Zeit<1ms TTL=128

Ping-Statistik für 192.168.8.199:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms

Your tests show that the VirtualBox net filter driver can successfully inject Ethernet frames in the direction of the host (ping) and in the direction of the network (DHCP), and that it can also intercept the Ethernet frames coming from both directions.

On an Ethernet cable, VirtualBox uses a separate Ethernet MAC address for the VM, so the LTE router sees two different MAC addresses connected to one of its LAN ports. Does the LTE router support that? For a test, try the following command while the VM is not running:

Code: Select all

cd "C:\Program Files\Oracle\VirtualBox"
VBoxManage setextradata "VM Name" VBoxInternal/Devices/e1000/0/LUN#0/Config/SharedMacOnWire 1

To remove that setting later on, repeat the command without the "1" at the end. Please provide another zipped VBox.log file so that we can verify that the setting has been changed successfully.

Other than that, you'll probably have to investigate on your LTE router. What type and model is it?

fth0 wrote:the LTE router sees two different MAC addresses connected to one of its LAN ports. Does the LTE router support that?

Mine does, I'm using it that way right now (Huawei B618s-22d Cat11). It's an Ethernet connection to the router (going through a switch - I wired my entire home for Ethernet), so the limitations of WiFi shouldn't be relevant. The fact that it uses LTE instead of ADSL to connect on the WAN side shouldn't IMO be relevant either.

I'm with you that an LTE router being that limited isn't very probable. I just wanted to try the "simple" shared MAC approach before giving detailed instructions for a Wireshark trace.

fth0 wrote:I'm with you that an LTE router being that limited isn't very probable. I just wanted to try the "simple" shared MAC approach before giving detailed instructions for a Wireshark trace.

I've got no clue if that LTE-Router supports that or not... but since I've got the same Issues on the company network I would suppose that not beeing a problem. I also have used that router successfully with Vmware and the "bridged - replicate physical network state" option.

But... before we go deeper I will try that on a different host machine, may there is something borked with that.
The host is an IPC with Win10-Enterprise LTSC straight out of the box. Maybe there is a windows-component missing that virtualbox needs?
I'll try that first an report back.

virtualbox.org

Guest-OS can only ping host from Bridged network

Guest-OS can only ping host from Bridged network

Re: Guest-OS can only ping host from Bridged network

Re: Guest-OS can only ping host from Bridged network

Re: Guest-OS can only ping host from Bridged network

Re: Guest-OS can only ping host from Bridged network

Re: Guest-OS can only ping host from Bridged network

Re: Guest-OS can only ping host from Bridged network

Re: Guest-OS can only ping host from Bridged network

Re: Guest-OS can only ping host from Bridged network

Re: Guest-OS can only ping host from Bridged network

Re: Guest-OS can only ping host from Bridged network

Re: Guest-OS can only ping host from Bridged network

Re: Guest-OS can only ping host from Bridged network

Re: Guest-OS can only ping host from Bridged network

Re: Guest-OS can only ping host from Bridged network