[12.6 Monterey]Can't work Bridge Network with Win10 Guest

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
apo2
Posts: 70
Joined: 18. Jan 2018, 20:49

[12.6 Monterey]Can't work Bridge Network with Win10 Guest

Post by apo2 »

I have updated my MacBook Air 2020 from macOS 10.15.7 Catalina to macOS 12.6 Monterey, today.
Bridge Network setting and Windows 10 Guest (Intel PRO/1000 MT virtualized network adaptor) worked well on macOS Catalina with VirtualBox 6.1.22.
VirtualBox 6.1.22 couldn't launch the Windows 10 Guest on Monterey, so I upgraded VirtualBox for Mac from 6.1.22 to 6.1.38.
Windows 10 Guest with VB 6.1.38 is running normally on macOS 12.6 Monterey with only NAT network (Intel PRO/1000 MT virtualized network adaptor).
I have tested Windows 10 Guest with VB 6.1.38 and Bridge Network setting, but Network Connectivity Status Indicator shows no Internet connection, and DNS isn't available.

What should I take for this issue that Bridge Network setting isn't working on Windows 10 Guest with VB 6.1.38 on macOS 12.6 Monterey ?
Please let me know how can I try to them.
Last edited by apo2 on 24. Sep 2022, 18:35, edited 1 time in total.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: [12.6 Monterey]Can't work Bridge Network with Win10 Guest

Post by scottgus1 »

Bridged won't work with Wi-Fi on Monterey, 'tis a known issue.

See Virtualbox Networks: In Pictures: Bridged Adapter for why Bridged does not always work on Wi-Fi, and note that an upgraded host OS includes new Wi-Fi drivers. Also please note the possible workaround.
apo2
Posts: 70
Joined: 18. Jan 2018, 20:49

Re: [12.6 Monterey]Can't work Bridge Network with Win10 Guest

Post by apo2 »

Hum, I see.

But, Bridged network via en0: Wi-Fi (Airport) is working with Windows 10 Guest (Intel PRO/1000 MT virtualized network adaptor) on macOS 10.13.6 High Sierra (another MacBook Pro), now.
VirtualBox(s) are same version (6.1.38). Will the issue be fixed in the future version of VirtualBox (i.e. VirtualBox 7.0) on Monterey and Ventura ?

I strongly hope that the issue in which Bridged network on WI-Fi will be fixed.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: [12.6 Monterey]Can't work Bridge Network with Win10 Guest

Post by scottgus1 »

Did you read the tutorial? Bridged fails because of the Apple Wi-Fi drivers, not because of any bug in Virtualbox, which there isn't one. High Sierra's Wi-Fi driver is lax and allows Bridged, so is Catalina's. Monterey's is strict and blocks Bridged. The tutorial very clearly explains this. If you are waiting for Virtualbox devs to fix Apple's Monterey Wi-Fi driver, prepare to get a lot older first.

How did setting a correct static IP address in the VM go?
apo2
Posts: 70
Joined: 18. Jan 2018, 20:49

Re: [12.6 Monterey]Can't work Bridge Network with Win10 Guest

Post by apo2 »

scottgus1 wrote: If you are waiting for Virtualbox devs to fix Apple's Monterey Wi-Fi driver, prepare to get a lot older first.

How did setting a correct static IP address in the VM go?
The static IP address in the VM can't go to fix connecting with localnet and internet also. The ping to default gateway did not respond.
Its true that Monterey's is strict and blocks Bridged. (Apple's security policy is too strict in recently.)
Last edited by apo2 on 25. Sep 2022, 03:52, edited 1 time in total.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: [12.6 Monterey]Can't work Bridge Network with Win10 Guest

Post by scottgus1 »

apo2 wrote:The static IP address in the VM can't go to fix connecting with localnet and internet all so. The ping to default gateway did not respond.
Post the output of ifconfig from the host terminal, and ipconfig /all from inside the Windows command prompt.
apo2
Posts: 70
Joined: 18. Jan 2018, 20:49

Re: [12.6 Monterey]Can't work Bridge Network with Win10 Guest

Post by apo2 »

scottgus1, thank you for your help.

Here line after is ifconfig from the Mac host.

Code: Select all

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
	inet 127.0.0.1 netmask 0xff000000 
	inet6 ::1 prefixlen 128 
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
	nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en4: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether ac:de:48:00:11:22 
	inet6 fe80::aede:48ff:fe00:1122%en4 prefixlen 64 scopeid 0x4 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (100baseTX <full-duplex>)
	status: active
ap1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
	options=400<CHANNEL_IO>
	ether 36:7d:da:58:1d:d4 
	media: autoselect
	status: inactive
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=6463<RXCSUM,TXCSUM,TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
	ether 14:7d:da:58:1d:d4 
	inet6 fe80::cc3:270d:3542:8c94%en0 prefixlen 64 secured scopeid 0x6 
	inet6 240d:0:200b:8e00:1045:89bf:980e:ceb6 prefixlen 64 autoconf secured 
	inet6 240d:0:200b:8e00:9d84:f8f4:b87b:7cc2 prefixlen 64 autoconf temporary 
	inet 192.168.1.7 netmask 0xffffff00 broadcast 192.168.1.255
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=460<TSO4,TSO6,CHANNEL_IO>
	ether ee:90:fb:ec:f1:80 
	media: autoselect <full-duplex>
	status: inactive
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=460<TSO4,TSO6,CHANNEL_IO>
	ether ee:90:fb:ec:f1:81 
	media: autoselect <full-duplex>
	status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=63<RXCSUM,TXCSUM,TSO4,TSO6>
	ether ee:90:fb:ec:f1:81 
	Configuration:
		id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
		maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
		root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
		ipfilter disabled flags 0x0
	member: en1 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 8 priority 0 path cost 0
	member: en2 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 7 priority 0 path cost 0
	nd6 options=201<PERFORMNUD,DAD>
	media: <unknown type>
	status: inactive
awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=400<CHANNEL_IO>
	ether 42:c6:b1:6d:0f:a0 
	inet6 fe80::40c6:b1ff:fe6d:fa0%awdl0 prefixlen 64 scopeid 0xa 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
llw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=400<CHANNEL_IO>
	ether 42:c6:b1:6d:0f:a0 
	inet6 fe80::40c6:b1ff:fe6d:fa0%llw0 prefixlen 64 scopeid 0xb 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
	inet6 fe80::baf6:63ac:93a5:41aa%utun0 prefixlen 64 scopeid 0xc 
	nd6 options=201<PERFORMNUD,DAD>
utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
	inet6 fe80::d9fc:c05e:60f2:721%utun1 prefixlen 64 scopeid 0xd 
	nd6 options=201<PERFORMNUD,DAD>
utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1000
	inet6 fe80::ce81:b1c:bd2c:69e%utun2 prefixlen 64 scopeid 0xe 
	nd6 options=201<PERFORMNUD,DAD>
utun3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
	inet6 fe80::95a2:4f96:6e23:ab2f%utun3 prefixlen 64 scopeid 0xf 
	nd6 options=201<PERFORMNUD,DAD>
utun4: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
	inet6 fe80::9578:161b:58c1:1913%utun4 prefixlen 64 scopeid 0x10 
And here line after is ipconfig /all from Windows 10 Guest.

Code: Select all

C:\Users\apo2>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : MOMO-VBOX
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter イーサネット:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
   Physical Address. . . . . . . . . : 08-00-27-4E-DE-27
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::5c47:3fc4:6acc:1b21%13(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.30(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 218628135
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-26-ED-77-2E-08-00-27-4E-DE-27
   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: [12.6 Monterey]Can't work Bridge Network with Win10 Guest

Post by scottgus1 »

apo2's host ifconfig wrote:en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
   ...
   inet 192.168.1.7 netmask 0xffffff00 broadcast 192.168.1.255
apo2's VM ipconfig /all wrote:Ethernet adapter イーサネット:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
   Physical Address. . . . . . . . . : 08-00-27-4E-DE-27
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::5c47:3fc4:6acc:1b21%13(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.30(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
Thanks for the info. It appears that you do have a correct static IP address in the VM. If you're certain that the VM is set to Bridged to your host's en0 adapter, and the VM's network 'cable' is connected, then I'm at the end of my ideas. The workarounds to not having Bridged available are in the tutorial.
Post Reply