3. However, I *cannot* connect to the 2.4GHz guest network (although I can see the SSID) and nothing shows up in the router messages.
When I use wpa_cli in interactive mode to try to manually connect, I have no problem using 'scan' to see the SSID.
However, when I try to (re)associate, I get the following error showing an "auth_failure".
Code:
<3>Trying to associate with SSID 'guest-2.4'
<3>Authentication with 6b:ad:d4:23:27:f0 timed out.
<3>CTRL-EVENT-DISCONNECTED bssid=6b:ad:d4:23:27:f0 reason=3 locally_generated=1
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=2 ssid="guest-2.4" auth_failures=1 duration=10 reason=CONN_FAILED
Note that I double/triple checked that the passphrase is correct (I am using WPA2-PSK) and verified using 'ps aux' on the router that the 'nas' line has the correct port (wl0.1), SSID and password.
If I disable security on the dd-wrt for the 2.4GHz guest network and then correspondingly in wpa_cli set key_mgmt to "NONE", then I can connect.
Changing the password didn't help.
Indeed, I seem to get the above error regardless of what password I use (whether correct or incorrect).
This was all working 2 days ago. I reloaded saved configs from when the 2.4GHz guest networking was working and rebooted but that *failed* to restore the 2.4GHz guest access.
So, I am stumped.
- It doesn't seem to be a HW wireless issue since I can access the 2.4GHz band via the standard, non-guest SSID
- It doesn't seem to be a configuration issue since restoring the old config didn't help.
Any ideas on what could be causing this and how to troubleshoot?
In particular why I am I getting a "CONN_FAILED" message?
Is there any way I can see what if any signaling is reaching the router (since /var/log/messages fails to show anything).. so that I can see why connections are being rejected?
Last edited by puterboy2 on Fri Jul 29, 2022 4:53; edited 1 time in total
Not sure if this is relevant but while wpa_cli showed that the bssid for the 2.4GHz guest network is 6b:ad:d4:23:27:f0, dd-wrt shows that wl0.1_hwaddr=6b:ad:d4:23:27:e0.
Note that the hwaddr for the other wireless interfaces (wl0, wl1, and wl1.1 seem to match the corresponding values for the bssid shown by a wpa_cli scan.)
Also note that the values for wlX.Y_hwaddr match the corresponding values from ifconfig on the router.
Similarly the values shown under wpa_cli for the bssid match the values for "wl -i wlX.Y bssid" on the router.
So there is an inconsistency between:
Code:
ifconfig wl0.1
wl -i wl0.1 bssid
I tried setting wl0.1_hwaddr=6b:ad:d4:23:27:f0 to match the bssid using 'nvram set' and 'nvram commit' but it didn't seem to persist or work. Similarly, I was unable to change it from the GUI (under Setup->Networking:Network Configuration wl0.1)
So wondering if the problem is a MAC address mismatch???
Posted: Tue Aug 02, 2022 3:05 Post subject: Solved but not sure exactly how/why this fixes it...
By assiduously comparing the nvram parameters between a working and a non-working router... and via trial-and-error, I was able to fix the problem by *unsetting* br1_hwaddr.
Even though the MAC address for br1_hwaddr did not itself conflict with the BSSID or the MAC address for wl0.1, somehow it created a problem... resulting in the BSSID for wl0.1 differing from the ifconfig (hardware?) MAC address for wl0.1 which presumably was the proximal cause for the problem.
It still would be good to understand how the BSSID is set and calculated relative to the ifconfig (hardware?) MAC address for wl0.1
And it would be helpful to know whether and how one can set the BSSID manually.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Tue Aug 02, 2022 11:22 Post subject:
Broadcom side IDK if its possible, never really looked into it, if egc says its possible, then it likely is but only via CLI I suspect and not via UI, Atheros you now can set BSSID in UI.
The setting for the BSSID is only for client/station mode.
For example, if you have multiple APs with the same SSID, you can tell the client to connect only to AP 1 and not to AP 2.
The BSSID is actually the physical MAC address of the WLAN interface.
VAPs are virtual interfaces and do not have a real MAC address.
But some devices and WLAN cards require a special MAC encoding for the virtual access point.
The MAC of the VAP is based on the MAC of the physical interface and usually only differs by one byte.
E.g.
11.22.33.44.55.66
11.22.33.44.55.67
If you can't change the MAC of the VAP in the tab "network" then the driver may not support it.
On my R7800 I can change the MAC addresses as I like.
I can also change the BSSID in the hostapd.conf - this changes the MAC displayed under ifconfig at the same time.
but as far as I know Broadcom devices do not use hostapd
Joined: 08 May 2018 Posts: 14129 Location: Texas, USA
Posted: Tue Aug 02, 2022 13:21 Post subject:
the-joker wrote:
Broadcom side IDK if its possible, never really looked into it, if egc says its possible, then it likely is but only via CLI I suspect and not via UI, Atheros you now can set BSSID in UI.
Broadcom being the poor cousin which is closed source its always the last to get some love.
ho1Aetoo wrote:
The setting for the BSSID is only for client/station mode.
And my magic crystal ball leads me to believe that this is shared code for all devices that support client/station modes, regardless of vendor hardware. The only thing I've seen that may negate my statement is in respect to brcmfmac driver, not dhd driver: