Add support to multiple wlan interfaces #6
Conversation
|
Oh fun @JoseGoncalves yeah this looks pretty... ps i discovered a more easy option and I am completely throwing this out.. ;) In Bullseye all we need is: and i'm working on the ap0.conf file right now.. https://rcn-ee.net/rootfs/debian-armhf/2021-09-22/ Regards, |
|
@JoseGoncalves and this udev rule with these two config: REgards, |
|
@RobertCNelson Neat! Using udev events instead of polling sysfs would definetly speed up wireless initialization on BBs. FYI, I use a similar approach to add a Mesh interface to my boards: I think that you shoud replace in 81-create-ap0-interface.rules |
|
@JoseGoncalves okay did the first one, then saw my email wasn't in sync with github... i'll add the ap0 (SoftAp0) hard code now too! and hardcoded SoftAp0/ap0 too: Regards, |
|
@JoseGoncalves i think i'm happy with this setup now, for an out of box usb0/usb1/SoftAp0/wlan0/etc.. Please test when your free, to see if it works for you mesh setup ;) https://rcn-ee.net/rootfs/debian-armhf/2021-09-23/ Now to hack in all the "mac" address.. Do you think users will understand how to edit 👍 Specially since the RPI uses wpa_supplicantj ? Regards, |
OK. When I have some spare time I will try it.
I think this will be no problem... there is a lot of (good) documentation available on how to config wireless interfaces with wpa_supplicant/hostapd, notably the official RPi docs: |
|
oh @JoseGoncalves i'm still building all the old images.. But with the new release of Debian 11 (Bullseye) i've taken the time to rewrite and cleanup years of cruft... Eventually there will be a console/iot/etc.. right now it's about getting the basics correct.. Regards, |
@RobertCNelson I've booted the 2021-09-27 image in a BBGW and everthing seems to run fine. When I tried to power down with the power button, the system halted but power remain applied, i.e., I still see some board's LEDs on. Seems that the PMIC is not being set to shutdown the board. Noticed also that the utility scripts that were previously stored in Going to test now with my Mesh setup... |
|
Found that the |
|
@RobertCNelson Just noticed that you have |
|
Sweet!!!! |
The same happens when I execute a While in buster, with proper power off, I get this: So, on buster the kernel receives the power down command, while in bullseye it's (wrongly) receiving the halt command. Maybe this is due to some device tree misconfiguration for PMIC, because I see this dmesg output in bullseye: while in buster I only see this: |
|
Pretty sure it's the kernel, so i'll need to look into that.. v5.4.x-ti: http://gfnd.rcn-ee.org:81/farm/uptime/pwr15-ser23-bbgw-5.4.106-ti-r35.log v5.10.x-ti: http://gfnd.rcn-ee.org:81/farm/uptime/pwr17-ser25-bbbw-5.10.59-ti-r18.log |
|
@RobertCNelson I've tested the bullseye image with my mesh setup and everything works fine, after some required changes;
Regarding wpasupplicant, there is currently a request to Debian's package maintainers to add mesh support: As I see that you are now building your own wpasupplicant package: can you enable mesh support on it? |
|
@JoseGoncalves can you share your mesh0 and wlan0 files, i'll add them to the templates directory.. i can also switch back to '86, we upgraded the firmware for you. ;) |
|
@RobertCNelson here goes my ##### wpa_supplicant configuration file for a Mesh Point (802.11s)
# For details see https://w1.fi/cgit/hostap/plain/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=/run/wpa_supplicant
ctrl_interface_group=netdev
max_peer_links=10
mesh_max_inactivity=30
country=COUNTRY_CODE
p2p_disabled=1
network={
ssid="MESH_NETWORK_SSID"
mode=5
frequency=MESH_NETWORK_FREQUENCY
key_mgmt=SAE
sae_password="MESH_NETWORK_PASSWORD"
}And this is my udev rule to add a mesh0 interface: This was based in information retreived from TI's SDK and SWAA166 Application Report . There is no added config for wlan0, I do not use it when setting up a mesh network. Regarding firmware, the 8.9.0.0.88 should be better for standard uses (client station and AP) as it solves some security issues (according with TI's changelog). So, I don't have a strong opinion to what firmware version shoud be the default on BBs. Please note that mesh does not work properly with mainline wl18xx driver. For proper operation you need to have driver R8.8. TI has documented this driver release on WiLink8 Linux Wi-Fi Driver Release R8.8 Build User's Guide. |
|
and pushed! rcn-ee/repos@5e154ef |
Recently I needed to add a second Wi-Fi interface to a BeagleBone Green Gateway via a USB adapter.
After doing that, I've noticed that the SoftAp0 interface was not being initialized.
Digging on this issue I found that the
bb-wl18xx-tetherscript was assuming that only one wlan interface would exist.This pull request changes this script to allow that BBs with multiple wlan interfaces have the AP functionality properly configured.