SRR60 Wireless2 no internet

[SonnyKS]

SRR60 with latest firmware downloaded.

Set in AP mode with static IP on LAN.

Wireless1 and Wireless2 enabled. Guest SSID disabled.

Clients can connect to Wireless1 just fine and access internet.

Clients get IP if connecting to Wireless2 but cannot get to internet unless check box for "Allow employees to see
each other and access my local network" is checked. But obviously I dont want to have that checked !  

[SonnyKS · Accepted solution]

@MrJoshW    Thanks for the offer.   Just uploaded new firmware V2.4.1.106 that seems to have fixed the issue.

[Amidala]

According to your description, I verified this version(2.4.0.114) and found no problems. Are you also in this version? Could you please send us the config file?

[davidcheok]

From my own experience, the system takes a while to engage. Leave it for 15-30 mins and see if it works as it should. 

[SonnyKS]

@Amidala Sure - Where do I send it the file?

[RaghuHR]

@SonnyKS  you upload into google drive or any such tool to upload debug logs and send via PM.

Thanks,

Raghu

[evan2]

@SonnyKS 

I see the issue using your config, because LAN IP is different from DHCP server,

I restore your config, OrbiPro br0 IP is static 192.168.1.10 in AP mode, but my DHCP is 192.168.30.x,

How do you set a static IP in AP mode?

WAN and LAN settings are gray out in AP mode, I can't set it.

[SonnyKS]

@evan2   Static IP is set for 192.168.1.10 and DHCP server is at 192.168.1.254

If you take the option to change the setting from Router to AP mode - it lets you set the static IP address and then it grays out the option once it is set in AP mode so you cannot change it unless you do a factory reset.

I have opened a cae with netgear support and they were able to replicate the issue so am awaiting their feedback on what to do next. 

[MrJoshW]

@SonnyKS Can you private message me the case number and I can take a look where it is at on the support process.

[SonnyKS · Accepted solution]

@MrJoshW    Thanks for the offer.   Just uploaded new firmware V2.4.1.106 that seems to have fixed the issue.