| 1 |
On Mon, Jul 16, 2012 at 10:13 AM, Tommy Bongaerts |
| 2 |
<tommy.bongaerts@×××××.com> wrote: |
| 3 |
> On Mon, Jul 16, 2012 at 09:42:54AM -0400, Michael Mol wrote: |
| 4 |
>> On Mon, Jul 16, 2012 at 8:45 AM, Tommy Bongaerts |
| 5 |
>> <tommy.bongaerts@×××××.com> wrote: |
| 6 |
>> > Hi, |
| 7 |
>> > |
| 8 |
>> > I'm running Gentoo on an Acer Travelmate 7750 laptop. This |
| 9 |
>> > particular laptop has a Broadcom wireless NIC that only works with |
| 10 |
>> > the proprietary Broadcom wl driver as provided by the broadcom-sta |
| 11 |
>> > ebuild. |
| 12 |
>> > |
| 13 |
>> > Wireless by itself works perfectly fine, but when I use virtualbox |
| 14 |
>> > with the virtual NIC bridged to my wlan0 interface, networking in |
| 15 |
>> > the guest OS doesn't work properly. |
| 16 |
>> > |
| 17 |
>> > I have made the following observations: |
| 18 |
>> > |
| 19 |
>> > * when the guest OS is configured to use DHCP it doesn't get an IP |
| 20 |
>> > from my DHCP server, but get an autoconfig IP instead |
| 21 |
>> > * however, I can see the DHCP requests towards my DHCP server in |
| 22 |
>> > Gentoo when monitoring the wlan0 interface with |
| 23 |
>> > # tcpdump -i wlan0 |
| 24 |
>> > * when I configure a static IP on the guest OS, I cannot ping from the |
| 25 |
>> > guest to the Gentoo host or my default gateway, but pinging from the |
| 26 |
>> > Gentoo host or my gateway to the guest OS works fine |
| 27 |
>> > |
| 28 |
>> > I manage my wireless NIC through /etc/conf.d/net, using |
| 29 |
>> > wpa_supplicant with the wext driver. I also tried using |
| 30 |
>> > networkmanager, but that gave the exact same result. |
| 31 |
>> > |
| 32 |
>> > Under Ubuntu 12.04 the network bridge between the vbox NIC and the |
| 33 |
>> > wireless NIC works fine. This is also with the proprietary wl |
| 34 |
>> > driver, same version and all. |
| 35 |
>> > |
| 36 |
>> > Anyone an idea what might be wrong with my setup? |
| 37 |
>> |
| 38 |
>> Just guesses: |
| 39 |
>> |
| 40 |
>> 1) ebroute rules blocking packets? |
| 41 |
>> 2) I've heard before that wireless bridging has issues. I can't |
| 42 |
>> explain the discrepancy between your experience on Ubuntu 12.04 and |
| 43 |
>> Gentoo. |
| 44 |
>> |
| 45 |
>> What kernel sources package are you using on Gentoo? Which kernel |
| 46 |
>> version are you using on Gentoo and on Ubuntu? |
| 47 |
> |
| 48 |
> I have no packet filtering enable on this system at all, so that's not |
| 49 |
> it. |
| 50 |
> |
| 51 |
> I have also heard of the bridging issues with wireless interfaces, but |
| 52 |
> since it works with Ubuntu 12.04 using the same driver I'm pretty sure |
| 53 |
> this is a config issue. |
| 54 |
> |
| 55 |
> On Gentoo I'm using gentoo-sources 3.3.8 and 3.4.4, both having the |
| 56 |
> same issue. The kernel in Ubuntu 12.04 is 3.2.0 I think. |
| 57 |
|
| 58 |
Then I'd guess it comes down to one of these possibilities: |
| 59 |
|
| 60 |
1) Perhaps Ubuntu is enabling something (either a kernel configuration |
| 61 |
option or something in sysctl.conf) that you're not, or you're |
| 62 |
enabling something they're not. Perhaps it's something that directly |
| 63 |
affects ebroute, or perhaps it's something like power management. |
| 64 |
|
| 65 |
Compare sysctl.conf on Ubuntu with the one on your Gentoo system. Also |
| 66 |
compare the configs of the running kernel. |
| 67 |
|
| 68 |
2) Perhaps gentoo-sources is applying a patch which causes bridging |
| 69 |
with the wireless to break. |
| 70 |
|
| 71 |
Trying kernel-sources may answer this. |
| 72 |
|
| 73 |
3) Perhaps there's been an upstream regression since 3.2.0. |
| 74 |
|
| 75 |
Perhaps using the 3.2 series of gentoo-sources would help you find this. |
| 76 |
|
| 77 |
4) Perhaps Ubuntu is adding a patch which fixes a bug or adds functionality. |
| 78 |
|
| 79 |
Short of looking at each patch Ubuntu's applying, I don't know how |
| 80 |
you'd figure this one out. |
| 81 |
|
| 82 |
-- |
| 83 |
:wq |
Archives