Hello, I do have two WAC505 devices setup in my network. Both are running exactly the same configuration with different SSIDs. Unfortunately I cannot connect to 5Ghz network on one of the devices.
I am trying to connect using my Oneplus 8T device and Ipad Pro 2022.
I tried changing experimenting with different channels to no avail.
Any help would be appreciated. I am running latest available firmware: V9.8.0.6
My main settings:
Parameters 5 GHz
Antenna 2x2
Wireless Mode 11ac
Channel / Frequency Auto (6)/2.437 GHz / 36/5.18 GHz
Here's part of the log:
Tue Jun 13 04:55:15 CEST 2023 nddmp[2456]: alarm : seqNo-[102], level-[INFO], info-[5A-6A-91-EA-82-B3 wireless client Disconnected]
Tue Jun 13 04:55:15 CEST 2023 nddmp[2456]: alarm : seqNo-[101], level-[INFO], info-[5A-6A-91-EA-82-B3 wireless client could not obtain IP address]
Tue Jun 13 04:55:15 CEST 2023 hostapd: wifi1vap0: STA 5a:6a:91:ea:82:b3 IEEE 802.11: Station deauthenticated due to reason code 3
Tue Jun 13 04:55:15 CEST 2023 hostapd: wifi1vap0: STA 5a:6a:91:ea:82:b3 IEEE 802.11: disconnected
Tue Jun 13 04:55:14 CEST 2023 kernel: [68948.655276] ieee80211_mlme_recv_deauth: [wifi1vap0]: Received deauth from 5a:6a:91:ea:82:b3 with reason 3
Tue Jun 13 04:55:14 CEST 2023 hostapd: wifi1vap0: STA 5a:6a:91:ea:82:b3 IEEE 802.11: disassociated
Tue Jun 13 04:54:57 CEST 2023 nddmp[2456]: alarm : seqNo-[100], level-[OTHER], info-[{"ip":"-","mac":"5A-6A-91-EA-82-B3","hname":"5A-6A-91-EA-82-B3","txR":"0 Kbps","rxR":"0 Kbps","ssid":"kobylewo5-base","dOs":"Unknown Device OS","dType":"Unknown Device Type","mode":"11A","status":"Authenticated","bssid":"08-02-8E-40-CF-50","chnl":"36","chWidth":"20/40/80 MHz","rssi":"28","state":"None","type":"wpa2","idle":"0","time":"00:00:00","txB":"876","rxB":"358","pmf":"none","vlanID":"2","Username":"Not Applicable","radio":"1"}]
Tue Jun 13 04:54:57 CEST 2023 configd[2265]: Error in geting IP from FP_DB [19125]
Tue Jun 13 04:54:56 CEST 2023 nddmp[2456]: alarm : seqNo-[99], level-[OTHER], info-[5A-6A-91-EA-82-B3 wireless client Connected]
Tue Jun 13 04:54:56 CEST 2023 hostapd: wifi1vap0: STA 5a:6a:91:ea:82:b3 WPA: pairwise key handshake completed (RSN)
Tue Jun 13 04:54:56 CEST 2023 hostapd: wifi1vap0: STA 5a:6a:91:ea:82:b3 WPA: received EAPOL-Key frame (4/4 Pairwise)
Tue Jun 13 04:54:56 CEST 2023 nddmp[2456]: alarm : seqNo-[98], level-[INFO], info-[5A-6A-91-EA-82-B3 wireless client Connected]
Tue Jun 13 04:54:56 CEST 2023 hostapd: wifi1vap0: STA 5a:6a:91:ea:82:b3 WPA: sending 3/4 msg of 4-Way Handshake
Tue Jun 13 04:54:56 CEST 2023 hostapd: wifi1vap0: STA 5a:6a:91:ea:82:b3 WPA: received EAPOL-Key frame (2/4 Pairwise)
Tue Jun 13 04:54:56 CEST 2023 configd[2265]: 13948: error in fetching sta details for mac = 5A-6A-91-EA-82-B3, iface = wifi1vap0
Tue Jun 13 04:54:56 CEST 2023 configd[2265]: Authentication Failed for client 5A-6A-91-EA-82-B3
Tue Jun 13 04:54:56 CEST 2023 configd[2265]: Error in geting IP from FP_DB [19125]
Tue Jun 13 04:54:56 CEST 2023 hostapd: wifi1vap0: STA 5a:6a:91:ea:82:b3 WPA: sending 1/4 msg of 4-Way Handshake
Tue Jun 13 04:54:56 CEST 2023 hostapd: [HOSTAPD] check_entry_exist: Entry not available for [5A-6A-91-EA-82-B3]
Tue Jun 13 04:54:56 CEST 2023 hostapd: hostapd_notif_assoc: Marking client's assoc state as 0
Tue Jun 13 04:54:56 CEST 2023 hostapd: wifi1vap0: STA 5a:6a:91:ea:82:b3 IEEE 802.11: associated
Tue Jun 13 04:54:56 CEST 2023 configd[2265]: EEM: Received Event: NEW_STA_ASSOC_EEM
Tue Jun 13 04:51:01 CEST 2023 nddmp[2456]: alarm : seqNo-[97], level-[INFO], info-[5A-6A-91-EA-82-B3 wireless client Disconnected]
Tue Jun 13 04:51:01 CEST 2023 hostapd: wifi1vap0: STA 5a:6a:91:ea:82:b3 IEEE 802.11: Station deauthenticated due to reason code 3
Tue Jun 13 04:51:01 CEST 2023 nddmp[2456]: alarm : seqNo-[96], level-[INFO], info-[5A-6A-91-EA-82-B3 wireless client could not obtain IP address]
Tue Jun 13 04:51:01 CEST 2023 hostapd: wifi1vap0: STA 5a:6a:91:ea:82:b3 IEEE 802.11: disconnected
Tue Jun 13 04:51:01 CEST 2023 kernel: [68695.254899] ieee80211_mlme_recv_deauth: [wifi1vap0]: Received deauth from 5a:6a:91:ea:82:b3 with reason 3
Tue Jun 13 04:51:01 CEST 2023 hostapd: wifi1vap0: STA 5a:6a:91:ea:82:b3 IEEE 802.11: disassociated
There is one device only listed in the log, 5a:6a:91:ea:82:b3 - the AP does say in info-[5A-6A-91-EA-82-B3 wireless client could not obtain IP address], following a complete four way handshake - perfectly correct.
Have your DHCP somehow configured to assign IP addresses to known MAC addresses only? Due to Apples **** Wi-Fi privacy MAC address randomisation and modern Android following the same "trend" - making it difficult (or almost impossible) for average network admins.
A factor in this issue is your wonderful idea configuring different SSIDs by AP, probably paired with Netgear's or other router makers Access Control or MAC Filtering with the access rule "Block all new devices from connecting". With this setting, if you add a new device, before it can access your network, you must enter its MAC address for an Ethernet connection and its MAC address for a Wi-Fi connection in the allowed list.
In some cases, your device will change its private Wi-Fi address. (more and ne fun and pun!):
If you erase all content and settings or reset network settings on the device, your device will use a different private address the next time it connects to that network.
Starting with iOS 15, iPadOS 15 and watchOS 8, if your device hasn’t joined the network in six weeks, it will use a different private address the next time it connects to that network.
And if you make your device forget the network, it will also forget the private address it used with that network, unless it has been less than two weeks since the last time it was made to forget that network.
At the end of the day, it's your own private network. There is no reason to make the network administration difficult or cumbersome. You know which devices are connecting, and what MAC addresses these units have (just like the serial number of the mobile phone SIM card which never changes for the obvious reasons - but having the same privacy issue Apple and the privacy freaks are having. So for your own network(s), you can safely disable the randomized MAC usage, and let the system use the device MAC for each of your own new wireless network name (SSID) added.
I use Nighthawk X4S R7800 as the main unit for the two WACs that I have.
While I do use MAC DHCP IP assignment, I use it only for my desktops.
The connectivity issue I described only applies to the specific WAC and only 5Ghz network. I can connect fine with the 2,4Ghz network. The coverage of both networks is great when I test it.
I tried with different smartphones, ipad, nintendo switch and the same issue always happens.
