[FIXED] OS X 10.7 GM - Bridged Networking

Temporary forum to discuss issues and problems during a VirtualBox Beta or Release Candidate phase.

[FIXED] OS X 10.7 GM - Bridged Networking

Postby AVonGauss » 9. Jul 2011, 09:07

It doesn't appear bridged networking is working on OS X 10.7 using an Ubuntu 10.04 guest bridged to the wireless adapter (en1). When using bridged the guest will not have access to the network, but if configured as NAT connectivity will be as expected. It's definitely an OS X 10.7 regression issue rather than a VB 4.1 issue.
Attachments
VBox.log
(86.46 KiB) Downloaded 5 times
AVonGauss
 
Posts: 19
Joined: 11. May 2007, 00:36
Location: Boynton Beach, FL

Re: BETA 2: OS X 10.7 GM - Bridged Networking

Postby Sasquatch » 9. Jul 2011, 12:29

And bridged to en0, your wired interface?
Read the Forum Posting Guide before opening a topic.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org

Retired from this Forum since OSSO introduction.
Sasquatch
Volunteer
 
Posts: 17800
Joined: 17. Mar 2008, 13:41
Location: /dev/random
Primary OS: Debian other
VBox Version: PUEL
Guest OSses: Windows XP, Windows 7, Linux

Re: BETA 2: OS X 10.7 GM - Bridged Networking

Postby AVonGauss » 10. Jul 2011, 20:18

When bridged to the wired network (en0), works as expected.
AVonGauss
 
Posts: 19
Joined: 11. May 2007, 00:36
Location: Boynton Beach, FL

Re: BETA 2: OS X 10.7 GM - Bridged Networking

Postby Sasquatch » 10. Jul 2011, 20:21

Then it's more likely to be a wireless security thing than a regression. Please do more thorough testing before calling it a regression.
Read the Forum Posting Guide before opening a topic.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org

Retired from this Forum since OSSO introduction.
Sasquatch
Volunteer
 
Posts: 17800
Joined: 17. Mar 2008, 13:41
Location: /dev/random
Primary OS: Debian other
VBox Version: PUEL
Guest OSses: Windows XP, Windows 7, Linux

Re: BETA 2: OS X 10.7 GM - Bridged Networking

Postby Perryg » 10. Jul 2011, 20:47

It's definitely an OS X 10.7 regression issue rather than a VB 4.1 issue.

Looks to me like that is what they said. But that's just me. :wink:
Perryg
Site Moderator
 
Posts: 25964
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX - Other

Re: BETA 2: OS X 10.7 GM - Bridged Networking

Postby Hachiman » 11. Jul 2011, 12:37

AVonGauss wrote:It doesn't appear bridged networking is working on OS X 10.7 using an Ubuntu 10.04 guest bridged to the wireless adapter (en1). When using bridged the guest will not have access to the network, but if configured as NAT connectivity will be as expected. It's definitely an OS X 10.7 regression issue rather than a VB 4.1 issue.


What is output of ifconfig -a on your guest when your vm attached to bridged networking to wireless adapter?
--
Kind regards
Sr. Software Engineer
Oracle Corporation
Vasily Levchenko

PS. Happy VBoxing.
Hachiman
Oracle Corporation
 
Posts: 94
Joined: 18. Dec 2008, 21:04
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Solaris, NetBSD

Re: BETA 2: OS X 10.7 GM - Bridged Networking

Postby AVonGauss » 11. Jul 2011, 22:08

Code: Select all   Expand viewCollapse view
ifconfig -a
eth0      Link encap:Ethernet  HWaddr 08:00:27:37:8c:86 
          inet6 addr: 2001:470:5:347:a00:27ff:fe37:8c86/64 Scope:Global
          inet6 addr: fe80::a00:27ff:fe37:8c86/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:36 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5303 (5.3 KB)  TX bytes:1774 (1.7 KB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:480 (480.0 B)  TX bytes:480 (480.0 B)



What's a bit strange is above you can see it saw the IPv6 announcement, but was unable to obtain an IPv4 address from the DHCP server yet it must have been working at some point since it did obtain DNS information from the DHCP server. <edit> - as was pointed out in a follow up post, the resolv.conf file was a stale version from a few hours prior rather than current.

Code: Select all   Expand viewCollapse view
cat /etc/resolv.conf
# Generated by NetworkManager
domain local
search local
nameserver 75.75.75.75
nameserver 75.75.76.76

Code: Select all   Expand viewCollapse view
ls -alh /etc/resolv.conf
-rw-r--r-- 1 root root 102 2011-07-11 01:11 /etc/resolv.conf


One of the changes in OS X 10.7 appears that it will now use DHCP-PD for IPv6 to obtain DNS information, not sure it factors in to the issue here but wanted to include that information and the host Mac's resolv.conf which does contain the IPv6 nameserver entry. I don't believe the Ubuntu 10.04 level supports this so I believe it is correct in not being present in the guest's "/etc/resolv.conf".

Code: Select all   Expand viewCollapse view
cat /etc/resolv.conf
#
# Mac OS X Notice
#
# This file is not used by the host name and address resolution
# or the DNS query routing mechanisms used by most processes on
# this Mac OS X system.
#
# This file is automatically generated.
#
domain local
nameserver 75.75.75.75
nameserver 75.75.76.76
nameserver 2001:470:20::2
Last edited by AVonGauss on 12. Jul 2011, 00:01, edited 2 times in total.
AVonGauss
 
Posts: 19
Joined: 11. May 2007, 00:36
Location: Boynton Beach, FL

Re: BETA 2: OS X 10.7 GM - Bridged Networking

Postby AVonGauss » 11. Jul 2011, 22:20

For comparison, when the Ubuntu guest is bridged via wired network.

Code: Select all   Expand viewCollapse view
 ifconfig -a
eth0      Link encap:Ethernet  HWaddr 08:00:27:37:8c:86 
          inet addr:192.168.1.108  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: 2001:470:5:347:a00:27ff:fe37:8c86/64 Scope:Global
          inet6 addr: fe80::a00:27ff:fe37:8c86/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:359 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:33599 (33.5 KB)  TX bytes:4771 (4.7 KB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:720 (720.0 B)  TX bytes:720 (720.0 B)
AVonGauss
 
Posts: 19
Joined: 11. May 2007, 00:36
Location: Boynton Beach, FL

Re: BETA 2: OS X 10.7 GM - Bridged Networking

Postby Sasquatch » 11. Jul 2011, 22:35

What you've shown above is that when the VM is in bridged mode attached to wifi, it does not have any connectivity at all. What you see in /etc/resolv.conf is what was left from the last DHCP configuration. The IPv6 address you see is it's link local address and is configured automatically when the interface is in RUNNING state (i.e. cable connected/link detected). This is always the case for a VM, because you have to tell it to disconnect the cable from the NIC settings under the Advanced option.
When you attach it to the LAN interface, you can clearly see the difference. Not only does it have a proper IPv4 address, it also has your advertised IPv6 address.

Please check your access point security settings. If it's set on MAC address filter, this can happen, because the VM is denied access due to it's MAC not being in the allowed list.
Read the Forum Posting Guide before opening a topic.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org

Retired from this Forum since OSSO introduction.
Sasquatch
Volunteer
 
Posts: 17800
Joined: 17. Mar 2008, 13:41
Location: /dev/random
Primary OS: Debian other
VBox Version: PUEL
Guest OSses: Windows XP, Windows 7, Linux

Re: BETA 2: OS X 10.7 GM - Bridged Networking

Postby AVonGauss » 11. Jul 2011, 22:49

Actually, if you look again you'll see that there is indeed a normal IPv6 2001:470 address provided by an HE tunnel when bridged wireless. You are correct about the "/etc/resolv.conf" in the guest, it definitely was a carry over from earlier this morning - sorry for not noticing that myself.

It is not an issue of MAC security configuration, there is no MAC security configured on the router. Bridged wireless stopped working under VB 4.0.10 after upgrading to OS X 10.7 GM. I waited until BETA 2 to see if the issue had already been corrected during the regular development cycle prior to reporting.
AVonGauss
 
Posts: 19
Joined: 11. May 2007, 00:36
Location: Boynton Beach, FL

Re: BETA 2: OS X 10.7 GM - Bridged Networking

Postby Sasquatch » 11. Jul 2011, 23:05

Ah, so you say that it happened on 4.0.10 too? Then this report is invalid, as this is only about bugs introduced in the beta. If you have the same problem on a final release like 4.0.10, then you should report it in the Bugtracker (separate account needed), not here.

I see now that you indeed got a proper IPv6 address in the Guest, sorry that I missed that. Must have been too focused on the IPv4 thing. Still, this is not the place to discuss this issue, it's not beta specific.
Read the Forum Posting Guide before opening a topic.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org

Retired from this Forum since OSSO introduction.
Sasquatch
Volunteer
 
Posts: 17800
Joined: 17. Mar 2008, 13:41
Location: /dev/random
Primary OS: Debian other
VBox Version: PUEL
Guest OSses: Windows XP, Windows 7, Linux

Re: BETA 2: OS X 10.7 GM - Bridged Networking

Postby AVonGauss » 11. Jul 2011, 23:55

Its not a breakage report, but unless its not reproducible I don't think I would consider it invalid or against the posted guidelines for this BETA or BETAs in general (sticky post). With the OS X 10.7 public release in the next week or two, it would seem like it would be something good to know if not already known especially while in a development cycle to be prioritized accordingly - especially if that OS release is intended to be supported by this upcoming VirtualBox version.
AVonGauss
 
Posts: 19
Joined: 11. May 2007, 00:36
Location: Boynton Beach, FL

Re: BETA 2: OS X 10.7 GM - Bridged Networking

Postby Sasquatch » 12. Jul 2011, 00:12

Yes, but the beta guidelines specifically say to report regressions and bugs that are not in previous versions. Since your issue happens on 4.0.10 too, it means that this is not the place to report nor discuss it. Sure, the beta is affected too, but that's only because the bug is in 4.0.10. So it really should be discussed in the bugtracker.
Read the Forum Posting Guide before opening a topic.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org

Retired from this Forum since OSSO introduction.
Sasquatch
Volunteer
 
Posts: 17800
Joined: 17. Mar 2008, 13:41
Location: /dev/random
Primary OS: Debian other
VBox Version: PUEL
Guest OSses: Windows XP, Windows 7, Linux

Re: [NO REGRESSION] OS X 10.7 GM - Bridged Networking

Postby AVonGauss » 16. Jul 2011, 03:46

FWIW; issue still occurs in 4.1 B3 but appears to be resolved now in 4.0.12.
AVonGauss
 
Posts: 19
Joined: 11. May 2007, 00:36
Location: Boynton Beach, FL

Re: [NO REGRESSION] OS X 10.7 GM - Bridged Networking

Postby Frank Mehnert » 18. Jul 2011, 13:44

Yeah, there was indeed a fix for bridged networking in 4.0.12 which could affect your problem and the same fix will be part of 4.1 final.
Frank Mehnert
Oracle Corporation
 
Posts: 2523
Joined: 7. Jun 2007, 09:11
Location: Dresden, Germany
Primary OS: Debian Lenny
VBox Version: PUEL
Guest OSses: Linux, Windows

Next

Return to VirtualBox Beta/Release Candidate Feedback

Who is online

Users browsing this forum: No registered users and 1 guest