Cannot connect to guest network on R7000/Kong r35550M

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Author Message
thunderhead
DD-WRT User


Joined: 11 Nov 2017
Posts: 136

PostPosted: Wed Apr 25, 2018 19:36    Post subject: Cannot connect to guest network on R7000/Kong r35550M Reply with quote
I setup a guest network on my 5 GHz radio using kong's guide but I am unable to connect to it. DD-WRT seems to reject my password which I have carefully verified as matching the one I am using for the guest SSID. I tried changing the password on DD-WRT several times with the same behavior.

Note that I can connect to my non-guest wifi just fine.

I don't see anything in the DD-WRT /var/log/messages when I try to connect. Is there another place I can look?

The error log from my laptop when I try:
Code:

Apr 25 14:31:05 laptop NetworkManager[790]: <warn>  [1524684665.7189] device (wlan0): Activation: (wifi) association took too long
Apr 25 14:31:05 laptop NetworkManager[790]: <info>  [1524684665.7190] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Apr 25 14:31:05 laptop NetworkManager[790]: <warn>  [1524684665.7215] device (wlan0): Activation: (wifi) asking for new secrets
Apr 25 14:31:07 laptop NetworkManager[790]: <info>  [1524684667.3033] device (wlan0): supplicant interface state: scanning -> inactive
Apr 25 14:31:10 laptop NetworkManager[790]: <info>  [1524684670.4312] device (wlan0): supplicant interface state: inactive -> disconnected
Apr 25 14:31:12 laptop NetworkManager[790]: <info>  [1524684672.9439] settings-connection[0x55ed634445d0,3b0bd7ea-55ba-4f11-996a-258685741dbf]: write: successfully commited (keyfile: update /etc/NetworkManager/system-connections/GST_5>
Apr 25 14:31:12 laptop NetworkManager[790]: <info>  [1524684672.9472] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Apr 25 14:31:12 laptop NetworkManager[790]: <info>  [1524684672.9481] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Apr 25 14:31:12 laptop NetworkManager[790]: <info>  [1524684672.9489] device (wlan0): Activation: (wifi) connection 'GST_5' has security, and secrets exist.  No new secrets needed.
Apr 25 14:31:12 laptop NetworkManager[790]: <info>  [1524684672.9491] Config: added 'ssid' value 'GST_5'
Apr 25 14:31:12 laptop NetworkManager[790]: <info>  [1524684672.9493] Config: added 'scan_ssid' value '1'
Apr 25 14:31:12 laptop NetworkManager[790]: <info>  [1524684672.9495] Config: added 'bgscan' value 'simple:30:-80:86400'
Apr 25 14:31:12 laptop NetworkManager[790]: <info>  [1524684672.9497] Config: added 'key_mgmt' value 'WPA-PSK'
Apr 25 14:31:12 laptop NetworkManager[790]: <info>  [1524684672.9499] Config: added 'psk' value '<hidden>'
Apr 25 14:31:12 laptop NetworkManager[790]: <info>  [1524684672.9694] device (wlan0): supplicant interface state: disconnected -> scanning
Apr 25 14:31:17 laptop NetworkManager[790]: <info>  [1524684677.2274] device (wlan0): supplicant interface state: scanning -> associating
Apr 25 14:31:17 laptop NetworkManager[790]: <info>  [1524684677.2941] device (wlan0): supplicant interface state: associating -> associated
Apr 25 14:31:25 laptop NetworkManager[790]: <info>  [1524684685.3542] device (wlan0): supplicant interface state: associated -> disconnected
Apr 25 14:31:25 laptop NetworkManager[790]: <info>  [1524684685.4546] device (wlan0): supplicant interface state: disconnected -> scanning
Apr 25 14:31:37 laptop NetworkManager[790]: <warn>  [1524684697.7200] device (wlan0): Activation: (wifi) association took too long
Apr 25 14:31:37 laptop NetworkManager[790]: <info>  [1524684697.7201] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Apr 25 14:31:37 laptop NetworkManager[790]: <warn>  [1524684697.7227] device (wlan0): Activation: (wifi) asking for new secrets
Apr 25 14:31:40 laptop NetworkManager[790]: <info>  [1524684700.0477] device (wlan0): supplicant interface state: scanning -> inactive
Apr 25 14:31:42 laptop NetworkManager[790]: <info>  [1524684702.8946] device (wlan0): supplicant interface state: inactive -> disconnected
Apr 25 14:31:51 laptop NetworkManager[790]: <info>  [1524684711.7453] settings-connection[0x55ed634445d0,3b0bd7ea-55ba-4f11-996a-258685741dbf]: write: successfully commited (keyfile: update /etc/NetworkManager/system-connections/GST_5>
Apr 25 14:31:51 laptop NetworkManager[790]: <info>  [1524684711.7467] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Apr 25 14:31:51 laptop NetworkManager[790]: <info>  [1524684711.7477] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Apr 25 14:31:51 laptop NetworkManager[790]: <info>  [1524684711.7485] device (wlan0): Activation: (wifi) connection 'GST_5' has security, and secrets exist.  No new secrets needed.
Apr 25 14:31:51 laptop NetworkManager[790]: <info>  [1524684711.7487] Config: added 'ssid' value 'GST_5'
Apr 25 14:31:51 laptop NetworkManager[790]: <info>  [1524684711.7489] Config: added 'scan_ssid' value '1'
Apr 25 14:31:51 laptop NetworkManager[790]: <info>  [1524684711.7491] Config: added 'bgscan' value 'simple:30:-80:86400'
Apr 25 14:31:51 laptop NetworkManager[790]: <info>  [1524684711.7493] Config: added 'key_mgmt' value 'WPA-PSK'
Apr 25 14:31:51 laptop NetworkManager[790]: <info>  [1524684711.7494] Config: added 'psk' value '<hidden>'
Apr 25 14:31:51 laptop NetworkManager[790]: <info>  [1524684711.7728] device (wlan0): supplicant interface state: disconnected -> scanning
Apr 25 14:31:55 laptop NetworkManager[790]: <info>  [1524684715.3473] device (wlan0): supplicant interface state: scanning -> disconnected
Apr 25 14:31:56 laptop NetworkManager[790]: <info>  [1524684716.0432] device (wlan0): supplicant interface state: disconnected -> associating
Apr 25 14:31:56 laptop NetworkManager[790]: <info>  [1524684716.1042] device (wlan0): supplicant interface state: associating -> associated
Apr 25 14:32:04 laptop NetworkManager[790]: <info>  [1524684724.1641] device (wlan0): supplicant interface state: associated -> disconnected
Apr 25 14:32:04 laptop NetworkManager[790]: <info>  [1524684724.2643] device (wlan0): supplicant interface state: disconnected -> scanning
Apr 25 14:32:16 laptop NetworkManager[790]: <warn>  [1524684736.7210] device (wlan0): Activation: (wifi) association took too long
Apr 25 14:32:16 laptop NetworkManager[790]: <info>  [1524684736.7211] device (wlan0): state change: config -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Apr 25 14:32:16 laptop NetworkManager[790]: <warn>  [1524684736.7221] device (wlan0): Activation: failed for connection 'GST_5'
Apr 25 14:32:16 laptop NetworkManager[790]: <info>  [1524684736.7229] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Apr 25 14:32:16 laptop NetworkManager[790]: <info>  [1524684736.7257] device (wlan0): set-hw-addr: set MAC address to 12:D0:C8:5F:4E:59 (scanning)
Apr 25 14:32:16 laptop NetworkManager[790]: <info>  [1524684736.7382] device (wlan0): supplicant interface state: scanning -> inactive
Apr 25 14:32:21 laptop NetworkManager[790]: <info>  [1524684741.3947] device (wlan0): supplicant interface state: inactive -> disconnected

_________________
*3x R7000 on DD-WRT v3.0-r36070M kongac (05/31/2018) both radios on/primary router.
*1x R7000 on DD-WRT v3.0-r39575M kongac (04/20/2019) both radios disabled configured as a switch.
*R7800 on OpenWRT 18.06.5
Sponsor
Dr_K
DD-WRT User


Joined: 23 Mar 2018
Posts: 438

PostPosted: Thu Apr 26, 2018 17:58    Post subject: Reply with quote
It should work

I've used the same guide on 2 separate routers successfully

Is guest set up on different subnets? It should be

Are you sure the security mode is correct type?

I use "WPA2 Personal" & WPA Algorithms are "AES"

Not sure if it'll help or not

In the webif on the Services tab under "Additional DNSMasq Options" add "log-dhcp" for more info in the log

_________________
Location 1
R6300V2- DD-WRT v3.0-r39345M kongac (04-03-19) Gateway
WNDR3400v1 DD-WRT.v3.0-r35531_mega-nv64k (03/26/18 ) Access Point
WRT160Nv3 DD-WRT ?v3?.0-r35531 mini (03/26/18 ) Access Point
WRT54GSv5 DD-WRT v24-r33555_micro_generic (10/20/17) Repeater
Location 2
R6300V2- DD-WRT v3.0-r39345M kongac (04/03/19) Gateway
R6300V2- DD-WRT v3.0-r39345M kongac (04/03/19) Access Point
WNDR3700v2 DD-WRT v3.0-r35531 std (03/26/18 ) Access Point
E1200 v2 DD-WRT v3.0-r35531 mega-nv64k (03/26/18 ) Gateway(for trivial reasons)
2 devices: SXT 5 ac (mipsbe) RB 6.45.1 (06/27/19) PTP Bridge (0.8km/0.5mi)tx/rx866.6Mbps-1GbpsLAN

Thank You <Kong> & BrainSlayer for ALL that you do also to everyone here that shares their knowledge
wabe
DD-WRT Guru


Joined: 17 Jun 2006
Posts: 693

PostPosted: Thu Apr 26, 2018 18:21    Post subject: Reply with quote
Works perfect for me too
_________________
AC-68U rev. C1 on Build 41586
AC-68U rev. A1 on Build 41328
AC-68U rev. A1 on Build 41218
thunderhead
DD-WRT User


Joined: 11 Nov 2017
Posts: 136

PostPosted: Thu Apr 26, 2018 19:46    Post subject: Reply with quote
@dr_k - Yes, they are on separate subnets. As well, I am using "WPA2 Personal" and "AES" ... I do have 2 virtuals: one for 2.4GHz and another for 5GHz. I deleted the one on 5GHz for now so I just have the one... let's see if that makes any difference.
_________________
*3x R7000 on DD-WRT v3.0-r36070M kongac (05/31/2018) both radios on/primary router.
*1x R7000 on DD-WRT v3.0-r39575M kongac (04/20/2019) both radios disabled configured as a switch.
*R7800 on OpenWRT 18.06.5
Dr_K
DD-WRT User


Joined: 23 Mar 2018
Posts: 438

PostPosted: Thu Apr 26, 2018 21:01    Post subject: Reply with quote
Number of virtual interfaces should not matter as long as each has it's own subnet & DHCP Server

I've had one on each band in the past with no issue

As a new test I just reread kong's guide and configured my WNDR3400v1 dd-wrt.v3.0-r35531_mega-nv64k (03/26/18 ) setup as a gateway....

It worked as described... I did do a save & apply between the configured pages & it didn't work till a reboot

I know the guide is short but re confirm all your settings

Not optimal but try turning wireless security off for virtual interface as a test

It's not the build as I have it working on a kong build older and newer then yours

This sounds like a cop out but dare I suggest a erase nvram might be due?

_________________
Location 1
R6300V2- DD-WRT v3.0-r39345M kongac (04-03-19) Gateway
WNDR3400v1 DD-WRT.v3.0-r35531_mega-nv64k (03/26/18 ) Access Point
WRT160Nv3 DD-WRT ?v3?.0-r35531 mini (03/26/18 ) Access Point
WRT54GSv5 DD-WRT v24-r33555_micro_generic (10/20/17) Repeater
Location 2
R6300V2- DD-WRT v3.0-r39345M kongac (04/03/19) Gateway
R6300V2- DD-WRT v3.0-r39345M kongac (04/03/19) Access Point
WNDR3700v2 DD-WRT v3.0-r35531 std (03/26/18 ) Access Point
E1200 v2 DD-WRT v3.0-r35531 mega-nv64k (03/26/18 ) Gateway(for trivial reasons)
2 devices: SXT 5 ac (mipsbe) RB 6.45.1 (06/27/19) PTP Bridge (0.8km/0.5mi)tx/rx866.6Mbps-1GbpsLAN

Thank You <Kong> & BrainSlayer for ALL that you do also to everyone here that shares their knowledge
whenagain
DD-WRT Novice


Joined: 09 Aug 2013
Posts: 13
Location: Houston, TX

PostPosted: Mon Nov 25, 2019 0:45    Post subject: Re: Cannot connect to guest network on R7000/Kong r35550M Reply with quote
thunderhead wrote:
I setup a guest network on my 5 GHz radio using kong's guide but I am unable to connect to it. DD-WRT seems to reject my password which I have carefully verified as matching the one I am using for the guest SSID. I tried changing the password on DD-WRT several times with the same behavior.

Note that I can connect to my non-guest wifi just fine.


I am having the exact same issue on my R7000.

"Kong's guide" seems to be unavailable. I have tried the wiki instructions with DNSmasq first then DHCPd, and this old simple guide.

Did you ever get this working?

_________________
Netgear R7000 v1 running DD-WRT build r40559
TP-Link TL-WR1043ND v1.10 running DD-WRT build r23204
Linksys WRT54GL running Tomato 1.28
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum