IGEL_comm_black_1000x174.png
  • IGEL Community

Users Unable to Connect to WiFi from IGEL Devices

IGEL Support has started tracking an issue that seems to be spreading. Last week, we began receiving reports from home users suddenly unable to connect to their home WiFi from IGEL devices that were working but suddenly couldn't connect.


So far, it's all the same symptoms, with no change to IGEL suddenly the device hangs at authenticating to the wireless network until it times out and fails.

Looking at the journal logs, it looks like the devices are not receiving an appropriate response from the router and disconnect.

In journal logs, we see the below entries repeatedly as it tries to reconnect, and the user will be prompted to enter a password again.


Feb 08 11:54:10 RBC-000211 nm_lan[53360]: wlan0 391 50 -> 60 reason 0 user_data=0x557f529f79e0
Feb 08 11:54:10 RBC-000211 nm_lan[53360]: wlan0 391 60 -> 40 reason 0 user_data=0x557f529f79e0
Feb 08 11:54:10 RBC-000211 nm_lan[53360]: wlan0 391 40 -> 50 reason 0 user_data=0x557f529f79e0
Feb 08 11:54:35 RBC-000211 NetworkManager[11158]: <warn>  [1612803275.8662] device (wlan0): Activation: (wifi) association took too long, failing activation
Feb 08 11:54:35 RBC-000211 NetworkManager[11158]: <info>  [1612803275.8663] device (wlan0): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Feb 08 11:54:35 RBC-000211 nm_lan[53360]: wlan0 391 50 -> 120 reason 53 user_data=0x557f529f79e0
Feb 08 11:54:35 RBC-000211 NetworkManager[11158]: <warn>  [1612803275.8683] device (wlan0): Activation: failed for connection 'wlan0-0'
Feb 08 11:54:35 RBC-000211 NetworkManager[11158]: <info>  [1612803275.8687] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Feb 08 11:54:35 RBC-000211 nm_lan[53360]: wlan0 391 120 -> 30 reason 0 user_data=0x557f529f79e0
Feb 08 11:54:35 RBC-000211 NetworkManager[11158]: <info>  [1612803275.8798] device (wlan0): supplicant interface state: scanning -> disconnected
Feb 08 11:54:35 RBC-000211 NetworkManager[11158]: <info>  [1612803275.8802] device (p2p-dev-wlan0): supplicant management interface state: scanning -> disconnected
Feb 08 11:54:35 RBC-000211 nm_lan[53360]: wlan0 422 returning authfailed
Feb 08 11:54:35 RBC-000211 nm_lan[53360]: wlan0 465 exiting main loop
Feb 08 11:54:35 RBC-000211 nm_lan[53360]: wlan0 3239 configuring wlan0 exiting with error 11

The Wireless NICs and endpoint models are all unique. The only thing in common with the device so far is that they are all cable providers (Rogers and Comcast's Xfinity) using what looks to be the same management software for their Gateways.


Rogers

  • Gateway: Easy Connect 21753 (TG3482ER3)

Xfinity

  • Gateway: Technicolor CGM4140COM

  • Software: GCM4140COM_4.6p7s1_PROD_sey

I wanted to see if anyone else is experiencing this and give a heads up that it may come your way.


If you are experiencing this issue, please read more on the 'Users Unable to connect to WiFi from IGEL Devices' thread in the IGEL Community. Not a member? Join Today!

Recent Blog Posts

Join the IGEL Community

  • White YouTube Icon
  • iconfinder_social_media_logo_github_1221
  • Subscribe to our RSS