NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Rourick9
Aug 19, 2021Aspirant
SXR80 - Wireless 3 (IoT) Client Interruptions
Hello,
I'm currently operating an SXR80 (FW V3.2.6.100) with 3x SXS80 satellites attempting to leverage the 3 non-guest wireless SSIDs. The issue I'm experiencing is that specifically on the Wireless 3 SSID, clients are experiencing connectivity issues including connection timeouts and loss of network access despite never disconnecting from the associated SSID. This connectivity issue does not occur on the other production SSID broadcast via the Wireless 2 settings.
Wireless 3 Settings are as follows:
Enable Wireless 3 Network
Enable SSID Broadcast
(disabled) Enable SSID Separation for 2.4G/5GHz
(enabled) VLAN Profile
WPA2-PSK [AES]
(disabled) Enable Bandwidth per SSID
---
SSID is tied to VLAN 5 with a VLAN profile (50)
---
Advanced Wireless Settings:
2.4GHz
(disabled) Enable SSID Broadcast [though I'm fairly certain this is disabled as the Admin SSID broadcast is disabled, though SSID 2/3 are enabled]
Enable 20/40 MHz Coexistence
Enable WMM (WiFi multimedia) settings
CTS/RTS Threshold - 2347
Preamble Mode - Automatic
Trasmit Power Control - 50% [noticed client's attempting to jump between APs during validation testing and hence dropped 2.4GHz Tx power]
5GHz
(disabled) Enable SSID Broadcast [correct if wrong, but again believe this is tied to Admin SSID as it was disabled with no user interaction after establishing SSIDs]
Enable WMM (WiFi multimedia) settings
---
Enable MU-MIMO
(disabled) Enable Fast Roaming
---
VLAN / Bridge Settings for VLAN ID 50:
(disabled) Client Isolation
(enabled) Network Isolation
The intended use of this SSID/VLAN is to provide a secondary "employee" network despite the GUI referencing it as IoT.
I've seen a few other posts on here with connectivity issues tied to seemingly random settings including Traffic Metering settings, however cannot see anything logically wrong with this config. Is there anyone else experiencing this issue, or noticing client interruptions on the Wireless 3 SSID? Perhaps this is a new bug? I've verified the issue persists across numerous client devices inclduing brand new M1 Apple devices leveraging 802.11ax, through legacy 802.11ac hardware.
While fairly adept at managing enterprise grade wireless this is seemingly ellusive. I appreciate any insight, and would be happy to provide additional details as needed.
Thank you
4 Replies
- RaghuHRNETGEAR Expert
Thank you for reaching us here.
Do you know those device experiencing issues are connected to router or satellite?
Let us know the distance between your router and satellite. Any obstruction like thick concrete wall etc? You can share your network diagram.
We need debug log to debug your issue. Please access your router and satellite UI by
1. https://<ip add>/debug.htm.
2. Click on Start Capture. Wait for the issue to happen.
3. Click on Save debug log.
You can upload the debug logs into google drive and send me link to download via PM.
Raghu
- Rourick9Aspirant
Thank you for the reply Raghu,
I applied the most recent sucurity hotfix a few days prior (3.2.6.102) to see if that would resolve the connection issues (should it be a hiccup in the firmware) however, it appears unseccessful.
The connection problem appears to persist no matter which AP the clients are connected to, and this includes 10 feet line of sight from 2 separate satellites for testing.
The solution is currently configured in a hub-and-spoke where each AP is directly connected via wireless backhaul to the main router.
I will work on collecting some debug captures to provide here. I did open a case 44974595 however, due to the timing was unable to call in before it auto archived.
Thank you
- Rourick9Aspirant
After further testing it appears that "something" is triggering the remote satellites to power cycle.. which is then in turn causing clients to associate with the next nearest AP explaining the client "networking interruption, slow connection, re-established fast connection" loop.
While Netgear evaluates the logs submitted, has anyone else noticed this behavior and more specifically when leveraging VLANs and multiple SSIDs? I'm hoping there's either some magic setting combo that can combat this in the meantime, or perhaps downgrading to an older firmware. These were deployed after an out of box update to 3.2.6.100 and thus I've got no historic data to leverage.
Thank you
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!