The physical interface (wl0) is configured as access point with WPA2 PSK. I also set-up a guest SSID as virtual interface (W0.1) with WPA2 PSK. This setup is working without any problems.
Now when i add an additional virtual interface (wl0.2) suddenly wl0 stops broadcasting. wl0.1 and wl0.2 keep on broadcasting.
Now when i again at an additional virtual interface (wl0.3), wl0 and wl0.1 stops broadcasting. Wl0.2 and wl0.3 keep on broadcasting.
Within the DDWRT GUI everything seems to work. The virtual interface are created. But on my laptop i can not select the SSIDs of wl0 and wl0.1 anymore. And also with an app WIFI Analyser on my phone i can see that the signal drops the moment i create an additional virtual interface and push [apply settings].
I restarted the R7000 multiple times but the problem persists.
* Is there somebody with a R7000 that can create two or more virtual interface to test whether this also the case on his/her router?
* Is somebody familiar with this problem and has a solution for it?
Thanks in advance!
LOG of the R7000:
Apr 03 20:15:42 217.122.190.147-1 kernel: br0: port 1(vlan1) entered forwarding state
Apr 03 20:15:42 217.122.190.147-1 kernel: br0: port 2(vlan2) entered forwarding state
Apr 03 20:15:42 217.122.190.147-1 kernel: br0: port 3(eth1) entered forwarding state
Apr 03 20:15:43 217.122.190.147-1 kernel: br0: port 4(wl0.1) entered forwarding state
Apr 03 20:15:43 217.122.190.147-1 kernel: br0: port 5(wl0.2) entered forwarding state
Apr 03 20:15:43 217.122.190.147-1 kernel: br0: port 6(wl0.3) entered forwarding state
Apr 03 20:15:45 217.122.190.147-1 kernel: br0: port 7(eth2) entered forwarding state
Apr 03 20:22:12 217.122.190.147-1 dropbear: Early exit: Terminated by signal
Apr 03 20:23:42 217.122.190.147-1 logger: : cron : cron daemon successfully stopped
Apr 03 20:23:43 217.122.190.147-1 process_monitor: Restarting cron (time sync change)
Apr 03 20:23:43 217.122.190.147-1 process_monitor: We need to re-update after 3600 seconds
Apr 03 20:23:43 217.122.190.147-1 process_monitor: set timer: 3600 seconds, callback: ntp_main()
Apr 03 20:23:43 217.122.190.147-1 logger: : cron : cron daemon successfully started
Apr 03 20:23:43 217.122.190.147-1 cron: (CRON) STARTUP (fork ok)
Apr 03 20:23:52 217.122.190.147-1 kernel: br0: port 7(eth2) entered forwarding state
Apr 03 20:23:52 217.122.190.147-1 kernel: br0: port 6(wl0.3) entered forwarding state
Apr 03 20:23:52 217.122.190.147-1 kernel: br0: port 5(wl0.2) entered forwarding state
Apr 03 20:23:52 217.122.190.147-1 kernel: br0: port 4(wl0.1) entered forwarding state
Apr 03 20:23:52 217.122.190.147-1 kernel: br0: port 3(eth1) entered forwarding state
Apr 03 20:23:52 217.122.190.147-1 kernel: br0: port 2(vlan2) entered forwarding state
Apr 03 20:23:52 217.122.190.147-1 kernel: br0: port 1(vlan1) entered forwarding state
Apr 03 20:23:52 217.122.190.147-1 logger: : NAS : NAS lan (wl0 interface) successfully started
Apr 03 20:23:52 217.122.190.147-1 logger: : NAS : NAS lan (wl0.1 interface) successfully started
Apr 03 20:23:52 217.122.190.147-1 logger: : NAS : NAS lan (wl1 interface) successfully started
Apr 03 20:23:53 217.122.190.147-1 logger: : klogd : kernel log daemon successfully stopped
Apr 03 20:23:53 217.122.190.147-1 kernel: klogd: exiting
Apr 03 20:23:53 217.122.190.147-1 logger: : syslogd : syslog daemon successfully stopped
Apr 03 20:23:53 217.122.190.147-1 kernel: klogd started: BusyBox v1.24.2 (2017-02-03 11:08:57 CET)
Apr 03 20:23:53 217.122.190.147-1 logger: : resetbutton : resetbutton daemon successfully started
Seen your post on Kong's Build Release 32170M.....
I do recall having upto 6 SSID on one router on older Kong Builds, don't recall the build numbers. But in any case, yes I do have 5 SSIDs running without any issues with Kong's Build 32170M, 3 SSIDs on 2.4Ghz and 2 SSIDs on 5Ghz.
Basically I leave most of the wireless setting at Default from an 'erase nvram && reboot'.
Command to all SSIDs, I Enable Implicit Beamforming & Optimize Multicast Traffic.
Wireless Security on all SSIDs are WPA2 Personal / AES with Default 3600 Key Renewal
For Advanced Wireless Settings ALL but 2 settings are Default. For the 2.4Ghz Beacon Interval = 225 and DTIM Interval = 2. The 5Ghz I use Beacon Interval = 150 and DTIM Interval = 3. They both add upto 450ms which works for my devices and help with all the SSIDs coming off those 3 antennas. _________________ Home Network on Telus 1Gb PureFibre - 10GbE Copper Backbone
2x R7800 - Gateway & WiFi & 3xWireGuard - DDWRT r53562 Std k4.9
Off Site 1
R7000 - Gateway & WiFi & WireGuard - DDWRT r54517 Std
E3000 - Station Bridge - DDWRT r49626 Mega K4.4
Off Site 2
R7000 - Gateway & WiFi - DDWRT r54517 Std
E2000 - Wired ISP IPTV PVR Blocker - DDWRT r35531
Seen your post on Kong's Build Release 32170M.....
I do recall having upto 6 SSID on one router on older Kong Builds, don't recall the build numbers. But in any case, yes I do have 5 SSIDs running without any issues with Kong's Build 32170M, 3 SSIDs on 2.4Ghz and 2 SSIDs on 5Ghz.
Basically I leave most of the wireless setting at Default from an 'erase nvram && reboot'.
Command to all SSIDs, I Enable Implicit Beamforming & Optimize Multicast Traffic.
Wireless Security on all SSIDs are WPA2 Personal / AES with Default 3600 Key Renewal
For Advanced Wireless Settings ALL but 2 settings are Default. For the 2.4Ghz Beacon Interval = 225 and DTIM Interval = 2. The 5Ghz I use Beacon Interval = 150 and DTIM Interval = 3. They both add upto 450ms which works for my devices and help with all the SSIDs coming off those 3 antennas.
Hi Mac913,
I tried it immediately after your post but I took some time to see whether it stayed stable. And it is! I reset my router before but the problem persist. But I guess the statement [erase nvram && reboot] did it. Now I'm able to have multiple VAPs. Thanks for the tip and also for sharing your configuration.