wl driver (Broadcom) does not receive ARP packets (broadcasts)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bcmwl (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
It seems that the wl driver in kernel-2.6.28-14 restricted modules (x86_64) does not receive ARP broadcast packets (possibly, it does not receive broadcast packets at all).
Symptom: have two hosts A (your machine with wl and Broadcom) and B on the same Ethernet network. Boot them up. Do *not* connect or ping B from A. At this point, the ARP cache on B does not know the MAC address for A. Try ssh from B to A, it won't find the host. Do a single ping from A to B (which creates an entry for A in B's ARP cache). ssh from B to A then works.
The problem can of course be worked around by hardcoding the MAC address of the Broadcom/wl host in the ARP caches of the other machines on the network, but this is quite unwieldy.
I suspect the driver does not process Ethernet broadcasts, but I may be wrong (I haven't checked).
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelMo
Package: linux-restricte
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-meta
Uname: Linux 2.6.28-14-generic x86_64
affects: | linux (Ubuntu) → bcmwl (Ubuntu) |
[This is an automated message. Apologies if it has reached you inappropriately.]
This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue.
If this bug really is a bug in the linux-meta package you can move it back to linux-meta and set the Status to Confirmed, or contact us on the #ubuntu-kernel channel on the FreeNode IRC server. Thanks.