Can't run multiple guest networks simultaneously

  • 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.

fr33z0n3r

Regular Contributor
Is this a bug? I'm trying to run multiple guest networks. Why are there 3 slots in the GUI, if I can't even run 2 of them?

Device: AC68U
 

Jack Yaz

Part of the Furniture
Define "can't run" - what happens when you enable them, or do you mean the GUI prevents you from turning them on?
 

fr33z0n3r

Regular Contributor
Version 384.19
This new SSID is a second 2.4Ghz Guest SSID - I have a 2.4Ghz and a 5Ghz Main SSID as well.

When I try to enable this 2nd Guest Network, it acts like it does it but it never actually appears in a wifi list on my phone. Yes, I know how to manage wifi. No its not hidden. No I didn't overlook it.

When I press F5 on the Guest Network page, the 2nd Guest SSID info disappears and shows the Enable button, while the first guest network I have is still displayed (and working fine).
 

RMerlin

Asuswrt-Merlin dev
Works for me. I can get two Guest Network running at once on my RT-AX88U, both are visible.
 

fr33z0n3r

Regular Contributor
I"m wondering if I'm hitting a limitation for my model? The 3 active SSIDs being a max? I reset the config for this version, and I only use it for basic firewall and these SSIDs. Would be strange if this was a hardware problem.
 

RMerlin

Asuswrt-Merlin dev
Lack of available NVRAM would be my first guess.
 

fr33z0n3r

Regular Contributor
Right now it says 62MB used of 256MB. Anyone have any other ideas?

Checking the log, I notice this, which sounds like a bug.

Code:
<15>1 2021-01-18T15:22:06-05:00 RT-AC68U-2AD8-A2BD388-C syslog - - - syslog: Error unlocking 5: 9 Bad file descriptor
<15>1 2021-01-18T15:22:06-05:00 RT-AC68U-2AD8-A2BD388-C syslog - - - syslog: Error unlocking 0: 9 Bad file descriptor


Here is the full debug log when trying to enable this feature. It starts at ~ 15:30:29 and finishes the progress "bar" at ~ 15:30:39

Code:
Jan 18 15:30:29 rc_service: httpds 261:notify_rc restart_wireless;restart_qos;restart_firewall;
Jan 18 15:30:29 syslog: Error unlocking 5: 9 Bad file descriptor
Jan 18 15:30:29 syslog: Error unlocking 0: 9 Bad file descriptor
Jan 18 15:30:30 kernel: device eth1 left promiscuous mode
Jan 18 15:30:30 kernel: br0: port 2(eth1) entering forwarding state
Jan 18 15:30:30 kernel: device eth2 left promiscuous mode
Jan 18 15:30:30 kernel: br0: port 3(eth2) entering forwarding state
Jan 18 15:30:30 kernel: device wl0.1 left promiscuous mode
Jan 18 15:30:30 kernel: br0: port 4(wl0.1) entering forwarding state
Jan 18 15:30:33 kernel: device eth1 entered promiscuous mode
Jan 18 15:30:33 kernel: br0: topology change detected, propagating
Jan 18 15:30:33 kernel: br0: port 2(eth1) entering forwarding state
Jan 18 15:30:33 kernel: br0: port 2(eth1) entering forwarding state
Jan 18 15:30:33 kernel: device eth2 entered promiscuous mode
Jan 18 15:30:33 kernel: br0: topology change detected, propagating
Jan 18 15:30:33 kernel: br0: port 3(eth2) entering forwarding state
Jan 18 15:30:33 kernel: br0: port 3(eth2) entering forwarding state
Jan 18 15:30:33 kernel: device wl0.1 entered promiscuous mode
Jan 18 15:30:33 kernel: br0: topology change detected, propagating
Jan 18 15:30:33 kernel: br0: port 4(wl0.1) entering forwarding state
Jan 18 15:30:33 kernel: br0: port 4(wl0.1) entering forwarding state
Jan 18 15:30:33 kernel: device wl0.2 entered promiscuous mode
Jan 18 15:30:33 kernel: br0: topology change detected, propagating
Jan 18 15:30:33 kernel: br0: port 5(wl0.2) entering forwarding state
Jan 18 15:30:33 kernel: br0: port 5(wl0.2) entering forwarding state
Jan 18 15:30:36 acsd: selected channel spec: 0x1003 (3)
Jan 18 15:30:36 acsd: Adjusted channel spec: 0x1003 (3)
Jan 18 15:30:36 acsd: selected DFS-exit channel spec: 0x1003 (3)
Jan 18 15:30:36 acsd: selected channel spec: 0x1003 (3)
Jan 18 15:30:36 acsd: Adjusted channel spec: 0x1003 (3)
Jan 18 15:30:36 acsd: selected channel spec: 0x1003 (3)
Jan 18 15:30:36 acsd: acs_set_chspec: 0x1003 (3) for reason APCS_INIT
Jan 18 15:30:38 acsd: selected channel spec: 0xe22a (44/80)
Jan 18 15:30:38 acsd: Adjusted channel spec: 0xe22a (44/80)
Jan 18 15:30:38 acsd: selected DFS-exit channel spec: 0xe22a (44/80)
Jan 18 15:30:38 acsd: selected channel spec: 0xe22a (44/80)
Jan 18 15:30:38 acsd: Adjusted channel spec: 0xe22a (44/80)
Jan 18 15:30:38 acsd: selected channel spec: 0xe22a (44/80)
Jan 18 15:30:38 acsd: acs_set_chspec: 0xe22a (44/80) for reason APCS_INIT
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:39 syslog: WLCEVENTD wlceventd_proc_event(466): eth1: Deauth_ind 8E:2C:BB:96:8C:84, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 18 15:30:40 syslog: Error unlocking 5: 9 Bad file descriptor
Jan 18 15:30:40 syslog: Error unlocking 0: 9 Bad file descriptor
Jan 18 15:30:40 syslog: WLCEVENTD wlceventd_proc_event(500): eth1: Auth 8E:2C:BB:96:8C:84, status: Successful (0)
Jan 18 15:30:40 syslog: WLCEVENTD wlceventd_proc_event(529): eth1: Assoc 8E:2C:BB:96:8C:84, status: Successful (0)
Jan 18 15:30:41 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
Jan 18 15:30:41 kernel: HTB: quantum of class 20001 is big. Consider r2q change.
Jan 18 15:30:41 kernel: HTB: quantum of class 10009 is big. Consider r2q change.
Jan 18 15:30:41 kernel: HTB: quantum of class 20009 is big. Consider r2q change.
Jan 18 15:30:41 kernel: HTB: quantum of class 30010 is small. Consider r2q change.
Jan 18 15:30:41 kernel: HTB: quantum of class 20010 is small. Consider r2q change.
Jan 18 15:30:41 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Jan 18 15:30:42 syslog: WLCEVENTD wlceventd_proc_event(500): wl0.1: Auth C8:3A:6B:E7:3B:1A, status: Successful (0)
Jan 18 15:30:42 syslog: WLCEVENTD wlceventd_proc_event(529): wl0.1: Assoc C8:3A:6B:E7:3B:1A, status: Successful (0)
 
Last edited:

RMerlin

Asuswrt-Merlin dev
Right now it says 62MB used of 256MB. Anyone have any other ideas?

That`s unlikely, the RT-AC68U has a total of 64 KB of nvram.
 

fr33z0n3r

Regular Contributor
ah, was reading from the main page in the UI.

But I think I found my issue. I set the new network to way too short a duration. I think it was stopping the network right after starting it. I didn't realize what that value would do. I figured it would boot a user after being connected for a specific timeframe, but it shuts down the SSID after that long instead.
 

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