NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi Pro Firmware update - V2.4.0.114
Just updated the firmware to the latest today. Nothing seems to have changed. 1) 2nd Wifi still gives a third open SSID (initially seems to work but 3rd open ssid appeared again after some time) 2...
1) 2nd Wifi still gives a third open SSID (initially seems to work but 3rd open ssid appeared again after some time)
Did you see the issue on 2.3.5.108? then update FW to 2.4.0.114, still see the issue,
if you see the issue on 2.3.5.108, then update to 2.4.0.114, but config don't change after update, so the issue still happen on 2.4.0.114,
Please disable WiFi 2 and Enagle again on 2.4.0.114, it won't see the issue again,
We will fix it in next maintance release.
Its not a prudent policy to put unknown clients on your company network. Doing so simply invites potential hacks and with the large variation of malware out there infesting various o/ses, it would be a matter of time one propagates into an internal client. I would think it would be a simple job to create say separate private network to host these 'guests' especially since your guest ssid is unsecured. Dont know but thats just my logic.
1) 2nd Wifi still gives a third open SSID (initially seems to work but 3rd open ssid appeared again after some time)
Did you see the issue on 2.3.5.108? then update FW to 2.4.0.114, still see the issue,
if you see the issue on 2.3.5.108, then update to 2.4.0.114, but config don't change after update, so the issue still happen on 2.4.0.114,
Please disable WiFi 2 and Enagle again on 2.4.0.114, it won't see the issue again,
We will fix it in next maintance release.
"Please disable WiFi 2 and Enagle again on 2.4.0.114, it won't see the issue again,
We will fix it in next maintance release."
Ok. Trying it now. Will update again if it fails.
Hahhaha. Disabling the wifi 2 and re-enabling has solved the 3rd ssid issue.
- Update:
1) Wifi 2 3rd ssid unsecured resolved.
2) Client segregration on wireless 2 resolved
Still unresolved - vpn client on separate subnet
Thank you for the quick responses and help.
Hopefully vpn issue can be resolved in the next update (without us having to resort to alternative fixes).
Once again, thank you.
davidcheok wrote:
2) Client segregration on wireless 2 resolvedThe client segregation is done on a pure L2 level - no VLAN, no dedicated subnetworks, all devices are on the same IP subnet. This was disputed many times before - not that I like it the way it's implemented.
davidcheok wrote:
Still unresolved - vpn client on separate subnet
Hopefully vpn issue can be resolved in the next update (without us having to resort to alternative fixes).Again: This depends on the capabilities of the OpenVPN client resp. the restricted privileges and Kernel access rights available on iOS and Android. The subnet you see is just an intermediate transport network for the VPN. The real disadvantages are in the fact that we have no control on the IP addresses assigned on the VPN subnet, and that Netgear does a many2one NAT for all VPN clients on that subnet, so all VPN clients appear to originate from the same LAN IP address.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
