iOS devices on 5Ghz now can't connect to internet, but can see local network

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

Richard H

Occasional Visitor
I have an ASUS RT-AC86U router, plus a Unifi AC-Lite AP to help with a poor reception area. I'd recently has some unreliability with the router which I think may have been caused by a filesystem on it filling up ("Argh. No free space left for GC." in log). With the help of some guidance from here I removed the offending file, plus did a full factory reset and restored my config. I also updated to the latest Asus firmware. That error has now gone away.

I am now left with something very strange. The router seems to be working for all my wired and wireless (2.4 & 5Ghz, Asus and Unifi connected) devices (including my partner's Android phone), except, my iPhone 8 and iPad Pro 10.5" (on iOS 14.2 & iPadOS 14.1). They now share a peculiar issue where they can connect via 5Ghz (Asus or Unifi AP), but when connected like that, they are unable to get out to the internet. They can connect to internal sites (such as Home Assistant running on a Pi4) fine, but when I try to go to a website, or use an app like Twitter or Facebook, they eventually give a connection error. A speedtest app eventually times out too.

I'm not seeing anything obviously problematic in the router log any more. Here's the last couple of hours' worth:

Nov 20 14:36:16 wlceventd: wlceventd_proc_event(491): eth5: Disassoc 62:3D:0F:0F:71:F9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 20 14:46:23 acsd: selected channel spec: 0x1008 (8)
Nov 20 14:46:23 acsd: Adjusted channel spec: 0x1008 (8)
Nov 20 14:46:23 acsd: selected channel spec: 0x1008 (8)
Nov 20 14:46:23 acsd: acs_set_chspec: 0x1008 (8) for reason APCS_CSTIMER
Nov 20 15:01:26 acsd: selected channel spec: 0x1008 (8)
Nov 20 15:01:26 acsd: Adjusted channel spec: 0x1008 (8)
Nov 20 15:01:26 acsd: selected channel spec: 0x1008 (8)
Nov 20 15:05:43 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc0090292a8 next ffffffc010c8f120 prev ffffffc010c8f120 rep_entry->list ffffffc010c8f120 next ffffffc0090292a8 prev ffffffc0090292a8
Nov 20 15:05:43 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc011b71de8 next ffffffc0139bc620 prev ffffffc0139bc620 rep_entry->list ffffffc0139bc620 next ffffffc011b71de8 prev ffffffc011b71de8
Nov 20 15:16:28 acsd: selected channel spec: 0x1803 (1l)
Nov 20 15:16:28 acsd: Adjusted channel spec: 0x1803 (1l)
Nov 20 15:16:28 acsd: selected channel spec: 0x1803 (1l)
Nov 20 15:16:28 acsd: acs_set_chspec: 0x1803 (1l) for reason APCS_CSTIMER
Nov 20 15:18:51 wlceventd: wlceventd_proc_event(510): eth6: Auth 08:E6:89:D0:39:2D, status: Successful (0)
Nov 20 15:18:51 wlceventd: wlceventd_proc_event(539): eth6: Assoc 08:E6:89:D0:39:2D, status: Successful (0)
Nov 20 15:24:42 wlceventd: wlceventd_proc_event(491): eth6: Disassoc 08:E6:89:D0:39:2D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 20 15:24:42 wlceventd: wlceventd_proc_event(510): eth5: Auth 62:3D:0F:0F:71:F9, status: Successful (0)
Nov 20 15:24:42 wlceventd: wlceventd_proc_event(510): eth5: Auth 62:3D:0F:0F:71:F9, status: Successful (0)
Nov 20 15:24:42 wlceventd: wlceventd_proc_event(539): eth5: Assoc 62:3D:0F:0F:71:F9, status: Successful (0)
Nov 20 15:24:42 wlceventd: wlceventd_proc_event(491): eth5: Disassoc 62:3D:0F:0F:71:F9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 20 15:24:42 wlceventd: wlceventd_proc_event(510): eth5: Auth 62:3D:0F:0F:71:F9, status: Successful (0)
Nov 20 15:24:42 wlceventd: wlceventd_proc_event(539): eth5: Assoc 62:3D:0F:0F:71:F9, status: Successful (0)
Nov 20 15:24:46 acsd: eth5: NONACSD channel switching to channel spec: 0x1001 (1)
Nov 20 15:25:22 wlceventd: wlceventd_proc_event(491): eth5: Disassoc 62:3D:0F:0F:71:F9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 20 15:25:23 wlceventd: wlceventd_proc_event(510): eth6: Auth 08:E6:89:D0:39:2D, status: Successful (0)
Nov 20 15:25:23 wlceventd: wlceventd_proc_event(539): eth6: Assoc 08:E6:89:D0:39:2D, status: Successful (0)
Nov 20 15:39:48 acsd: selected channel spec: 0x1903 (5u)
Nov 20 15:39:48 acsd: Adjusted channel spec: 0x1903 (5u)
Nov 20 15:39:48 acsd: selected channel spec: 0x1903 (5u)
Nov 20 15:39:48 acsd: acs_set_chspec: 0x1903 (5u) for reason APCS_CSTIMER
Nov 20 15:54:51 acsd: selected channel spec: 0x1903 (5u)
Nov 20 15:54:51 acsd: Adjusted channel spec: 0x1903 (5u)
Nov 20 15:54:51 acsd: selected channel spec: 0x1903 (5u)
Nov 20 16:09:53 acsd: selected channel spec: 0x1803 (1l)
Nov 20 16:09:53 acsd: Adjusted channel spec: 0x1803 (1l)
Nov 20 16:09:53 acsd: selected channel spec: 0x1803 (1l)
Nov 20 16:09:53 acsd: acs_set_chspec: 0x1803 (1l) for reason APCS_CSTIMER
Nov 20 16:21:18 wlceventd: wlceventd_proc_event(474): eth6: Deauth_ind 08:E6:89:D0:39:2D, status: 0, reason: Disassociated due to inactivity (4)
Nov 20 16:21:18 wlceventd: wlceventd_proc_event(491): eth6: Disassoc 08:E6:89:D0:39:2D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 20 16:21:37 wlceventd: wlceventd_proc_event(510): eth6: Auth 08:E6:89:D0:39:2D, status: Successful (0)
Nov 20 16:21:37 wlceventd: wlceventd_proc_event(539): eth6: Assoc 08:E6:89:D0:39:2D, status: Successful (0)
Nov 20 16:24:55 acsd: selected channel spec: 0x1803 (1l)
Nov 20 16:24:55 acsd: Adjusted channel spec: 0x1803 (1l)
Nov 20 16:24:55 acsd: selected channel spec: 0x1803 (1l)
Nov 20 16:37:49 wlceventd: wlceventd_proc_event(474): eth6: Deauth_ind DC:DC:E2:70:A9:36, status: 0, reason: Disassociated due to inactivity (4)
Nov 20 16:37:49 wlceventd: wlceventd_proc_event(491): eth6: Disassoc DC:DC:E2:70:A9:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 20 16:37:58 wlceventd: wlceventd_proc_event(474): eth6: Deauth_ind 8A:4F:92:EE:DC:D1, status: 0, reason: Disassociated due to inactivity (4)
Nov 20 16:37:58 wlceventd: wlceventd_proc_event(491): eth6: Disassoc 8A:4F:92:EE:DC:D1, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 20 16:39:58 acsd: selected channel spec: 0x1903 (5u)
Nov 20 16:39:58 acsd: Adjusted channel spec: 0x1903 (5u)
Nov 20 16:39:58 acsd: selected channel spec: 0x1903 (5u)
Nov 20 16:39:58 acsd: acs_set_chspec: 0x1903 (5u) for reason APCS_CSTIMER


Can anyone think of any reason this might happen, or suggest how I might be able to get some more debug info from the router maybe?
 

L&LD

Part of the Furniture
Repeat the full reset to factory defaults on the firmware you want to use, now.

Do not use the backup config file to configure the router. Do it minimally and manually (M&M Config, see the link in my signature below) and do not 'blindly' use settings, scripts, or other customizations 'just because they worked' before.

Get the router working as noted above, add customizations one at a time, testing that the network, works, for an extended period after each change. Do not configure everything all at once (it won't help you track anything down).
 

dave14305

Part of the Furniture
These days its worth testing iOS devices again after disabling Private Addressing in the WiFi settings for your SSID. New feature in 14.x.
 

Richard H

Occasional Visitor
Repeat the full reset to factory defaults on the firmware you want to use, now.

Do not use the backup config file to configure the router. Do it minimally and manually (M&M Config, see the link in my signature below) and do not 'blindly' use settings, scripts, or other customizations 'just because they worked' before.

Get the router working as noted above, add customizations one at a time, testing that the network, works, for an extended period after each change. Do not configure everything all at once (it won't help you track anything down).

Thank you very much, I wished I'd have seen your signature links before!

My partner is still working, so I don't have the option to do a full reset for a while. Looking through your "Steps to try first" though, I realised I hadn't tried a guest network, so I created a simple 5GHz one. Both my iOS devices connected to this, and could see the internet with no issues! Even more surprising though, I "forgot" the problematic network on my devices, and reconnected to it again and that too is now working again for both of them! I'll leave alone for now and see if this really is a long term fix (for reasons I don't understand...). If not, then I'll return to your excellent page of links and follow through with the M&M suggestion.

Thanks again!
 

L&LD

Part of the Furniture

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top