Bug #727
open
brcmfmac having problems in AP + station mode
Added by Hammel almost 4 years ago.
Updated 4 months ago.
Category:
04 - Root File System
Description
In Ironman the brcmfmac wifi is being used in both AP and station mode at the same time. "iw list" shows this configuration is supported. However, if you bring up wlan0 and uap0 as has been done with other wifi dongles the brcmfmac will disconnect the station (wifi client) when it brings up the AP. This seems to be the same as other dongles and the solution was
- bring up wlan0
- bring up uap0
- bring up wlan0 again
But the last step doesn't work with brcmfmac. There is a possible solution here but I've not tried it yet. Some googling shows this driver disables the the station when ap is started and doesn't allow it to come back up. A fix was posted in 2018 but that doesn't appear to be in either RPi Linux 4.19.y or next branch. Not sure if there is a driver fix anywhere else.
Barring a driver fix and the potential workaround fixing this I'll have to disable brcmfmac in Ironman and use a dongle. Disabling will have to include removing or renaming the driver because S10mdev will load the driver automatically if it's there and simply rmmod'ing the driver later will cause the dongle to come up as wlan1, which we don't want.
- % Done changed from 0 to 20
New firmware does not fix the problem. The possible workaround doesn't really do anything I'm not already doing. I'm going to try one other thing: bring up wlan0 without wpa_supplicant, bring up uap0 then bring up wpa_supplicant on wlan0.
- % Done changed from 20 to 50
No, it doesn't work. It's the driver (and/or firmware). I simply can't use it with Ironman.
Falling back to a wifi dongle as we used previously. I'll disable the brcmfmac driver in the build via a config app, like I do with Xeon.
- Status changed from In Progress to Closed
- % Done changed from 50 to 100
Completed. I've added the package (ironmancfg) to GitLab and integrated it with Ironman's meta build.
Tested, committed and pused (both the new package and meta).
Closing issue.
- Status changed from Closed to In Progress
- Priority changed from Immediate to Urgent
- % Done changed from 100 to 10
- Severity changed from 01 - Critical to 04 - Low
I'm reopening this as it's been some time since I tried it. If I can get both working at the same time on the RPi 3 then I can simplify the piplayer (pinet app), for example, not to mention Ironman.
Here is a discussion on the same topic. Start reading from this post.
See also this post on superuser.com which describes more detailed configuration information that tells if the device does or does not support simultaneous modes or this "blog post"https://imti.co/iot-wifi/#legacy-instructions-the-manual-way that describes the software setup.
Basically what matters is if the brcm device supports simultaneous modes. For things like PiPlayer w/ the pinet app we only need to be in one mode or the other so brcm should work fine. If it's not working then there may be some other problem - like assuming device names as they come from usb wifi sticks vs the onboard brcm devie.
There are also tuning paramters that can be added to S40network.
- Target version changed from 2.0 - Harkonnen to 3.0 - Corrino
Also available in: Atom
PDF
Updated by