Hi,
i want to use b43 on older broadcom wireless routers with openwrt, but
there seems to be a problem: The router doesn't send beacons in adhoc
mode (verified with wireshark), which means users can't see the network
in a network scan. So is there a problem in the adhoc implementation
with b43? Could someone please have a look at this? It is preventing us
from using b43 in our mesh for too long now.
Some Infos about hardware/software used:
Router:
Siemens SE505 (very similar to wrt54g), Broadcom 4712 WLAN (core revision 7)
Software:
Openwrt Backfire r28226
kmod-b43 - 2.6.32.27+2011-08-26-1
kmod-b43legacy - 2.6.32.27+2011-08-26-1
kmod-cfg80211 - 2.6.32.27+2011-08-26-1
kmod-mac80211 - 2.6.32.27+2011-08-26-1
Kind regards, Manuel
On Sun, 18 Sep 2011 00:13:32 +0200
Rafał Miłecki <[email protected]> wrote:
> 2011/9/17 Manuel Munz <[email protected]>:
> > i want to use b43 on older broadcom wireless routers with openwrt, but
> > there seems to be a problem: The router doesn't send beacons in adhoc
> > mode (verified with wireshark), which means users can't see the network
> > in a network scan. So is there a problem in the adhoc implementation
> > with b43? Could someone please have a look at this? It is preventing us
> > from using b43 in our mesh for too long now.
adhoc is not tested a lot with b43 and nobody is really interested in it.
I _think_ it used to work, however.
You should probably compare AP vs adhoc codepaths. AP mode an adhoc are very
similar with only tiny differences in the driver.
> > Router:
> > Siemens SE505 (very similar to wrt54g), Broadcom 4712 WLAN (core revision 7)
>
> Please give us at least
> lspci -nn | grep 14e4
This is an embedded device.
--
Greetings, Michael.
On 17.09.2011 23:43, Manuel Munz wrote:
> Hi,
>
> i want to use b43 on older broadcom wireless routers with openwrt, but
> there seems to be a problem: The router doesn't send beacons in adhoc
> mode (verified with wireshark), which means users can't see the network
> in a network scan. So is there a problem in the adhoc implementation
> with b43? Could someone please have a look at this? It is preventing us
> from using b43 in our mesh for too long now.
>
Hi,
after trying various things i came up with the following patch which
seems to address the issue for me.
regards, Manuel
2011/9/17 Manuel Munz <[email protected]>:
> i want to use b43 on older broadcom wireless routers with openwrt, but
> there seems to be a problem: The router doesn't send beacons in adhoc
> mode (verified with wireshark), which means users can't see the network
> in a network scan. So is there a problem in the adhoc implementation
> with b43? Could someone please have a look at this? It is preventing us
> from using b43 in our mesh for too long now.
>
> Some Infos about hardware/software used:
>
> Router:
> Siemens SE505 (very similar to wrt54g), Broadcom 4712 WLAN (core revision 7)
Please give us at least
lspci -nn | grep 14e4
dmesg | grep b43
--
Rafał
On 18.09.2011 00:13, Rafał Miłecki wrote:
> Please give us at least
> lspci -nn | grep 14e4
> dmesg | grep b43
>
Hi,
here is the info you requested:
# dmesg |grep b43
b43-phy0: Broadcom 4712 WLAN found (core revision 7)
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
# lspci -nn | grep 14e4
00:00.0 Host bridge [0600]: Broadcom Corporation BCM47xx V.92 56k modem
[14e4:4712] (rev 01)
00:01.0 Host bridge [0600]: Broadcom Corporation BCM47xx V.92 56k modem
[14e4:4712] (rev 01)
00:02.0 Host bridge [0600]: Broadcom Corporation BCM47xx V.92 56k modem
[14e4:4712] (rev 01)
00:03.0 Host bridge [0600]: Broadcom Corporation BCM47xx V.92 56k modem
[14e4:4712] (rev 01)
00:04.0 Host bridge [0600]: Broadcom Corporation BCM47xx V.92 56k modem
[14e4:4712] (rev 01)
00:05.0 Host bridge [0600]: Broadcom Corporation BCM47xx V.92 56k modem
[14e4:4712] (rev 01)
00:06.0 Host bridge [0600]: Broadcom Corporation BCM47xx V.92 56k modem
[14e4:4712] (rev 01)
00:07.0 Host bridge [0600]: Broadcom Corporation BCM47xx V.92 56k modem
[14e4:4712] (rev 01)
00:08.0 Host bridge [0600]: Broadcom Corporation BCM47xx V.92 56k modem
[14e4:4712] (rev 01)
00:09.0 Host bridge [0600]: Broadcom Corporation BCM47xx V.92 56k modem
[14e4:4712] (rev 01)
00:0a.0 Host bridge [0600]: Broadcom Corporation BCM47xx V.92 56k modem
[14e4:4712] (rev 01)
00:0b.0 Host bridge [0600]: Broadcom Corporation BCM47xx V.92 56k modem
[14e4:4712] (rev 01)
00:0c.0 Host bridge [0600]: Broadcom Corporation BCM47xx V.92 56k modem
[14e4:4712] (rev 01)
00:0d.0 Host bridge [0600]: Broadcom Corporation BCM47xx V.92 56k modem
[14e4:4712] (rev 01)
00:0e.0 Host bridge [0600]: Broadcom Corporation BCM47xx V.92 56k modem
[14e4:4712] (rev 01)
00:0f.0 Host bridge [0600]: Broadcom Corporation BCM47xx V.92 56k modem
[14e4:4712] (rev 01)
The device has no 56k modem, so i guess the pciutils database is wrong here.
Regards, Manuel
On 09/18/2011 04:35 PM, Manuel Munz wrote:
> On 17.09.2011 23:43, Manuel Munz wrote:
>> Hi,
>>
>> i want to use b43 on older broadcom wireless routers with openwrt, but
>> there seems to be a problem: The router doesn't send beacons in adhoc
>> mode (verified with wireshark), which means users can't see the network
>> in a network scan. So is there a problem in the adhoc implementation
>> with b43? Could someone please have a look at this? It is preventing us
>> from using b43 in our mesh for too long now.
>>
>
> Hi,
>
> after trying various things i came up with the following patch which
> seems to address the issue for me.
I confirmed your fix with an ad-hoc connection from one b43 device to another.
Your patch needs to be reformatted to satisfy kernel requirements. I will take
care of that for you, but you need to read Documentation/SubmittingPatches.
Good work to find the fix.
Larry