NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
SXK80 - Firmware Version 4.2.3.102 bug
I found a bug in the firmware, after restoring the factory settings, when the ISP is on the 192.168.1.0/24 network segment, the device will automatically switch to the 10.0.00/24 network segment, and at this time when accessing the management page on the web site, a page "Your connection is not private" will appear, but this problem does not occur on the 192.168.1.0/24 network segment(meaning I need to disconnect from the WAN port of the ISP box first).
After testing, I found that this is caused by the NCSI test failure of windows 10, it should be caused by the failure of NCSI test in China, but why there is no NSCI test in 192.168.1.0/24 network segment when accessing the web administrator?
The current temporary solution is that I can either disable NCSI group policy in windows 10 on the 10.0.0.0/24 network segment, or I can only manually re-visit the official web page by typing "thisisunsafe" in the browser.
So I hope Netgear will fix this bug completely in the next firmware release.
Please note that need to clear your browser's cookies to reproduce this issue, not only that, but it also affects NMRP and TFTP firmware rewriting on the 10.0.0.0/24 network segment, after testing, TFTP tools get write errors when working on this network segment.
10.0.0.110.0.0.1-210.0.0.1-310.0.0.1-4192.168.1.1192.168.1.1-2
shejialun wrote:
I just don't understand why it would fail to run NSCI on an SXK80 device after restoring factory settings and switching to a 10.x subnet.
Don't worry, me neither. Simply no time to waste more time on this special case. Keep in mind not many users have to factory default, and all this in the double-NAT context.
Is the problem prohibitive for bringing up a SKX80 (or for the sake of it the similar SXK50 or SXK30 system) from a factory default re-config?
Realistically, 99.9x% of these systems are configured once, and run forever. There it goes the expectation for a utility, beyond plain standard tftp - available on many different platforms and OSes. If it's not broken already as of writing, unlikely Netgear does spend time and resources on this 80/50/30 product line.
For my part, I'm done with this, as I don't own such one of these product, and never got one for Beta testing. Other community members seem to have the better contact to the Orbi Pro router team than me. I'm just yet another community member trying to help where he can. Netgear does not care for us at all. We're accepted to spend time and effort for free, but this is the end for now. One day, if I find a pre-loved European device, I might be willing to buy one for some Cents. Just like the BR500 I own for the fun or pun of it.
Said this: Sorry for asking silly questions - now you understand, why.
16 Replies
shejialun wrote:
I found a bug in the firmware, after restoring the factory settings, when the ISP is on the 192.168.1.0/24 network segment, the device will automatically switch to the 10.0.00/24 network segment, ....
This isn't a bug - this is a long standing feature and implemented on all Netgear routers. Both 192.168.0.0/24 and 192.168.1.0/24 IP subnets are included when I have this right. When connecting the WAN to any device, like another NAT router for example, the default LAN subnet is changed from the 192.168.1.0/24 (and 192.168.0.0/24), the DHCP server is reconfigured.
Sigh, this can cause a lot of work if people "just for a test" connect the WAN to such a subnet, and the user does prefer not to factory default again.
Hello schumaku
I think you misunderstood or I didn't explain clearly.
When the WAN port of the device is connected to subnet 192.168.1.0/24, the LAN of the device switches to subnet 10.0.0.0/24, which is not a problem, because I was using an R7000 before using the SXK80, and it already had this feature.
The bug I'm talking about is that when the device's LAN is working on subnet 192.168.1.0/24, it will not activate the windows 10 client's NSCI function, but when the device switches to subnet 10.0.0.0/24 subnet, it will activate the windows 10's NCSI function to the extent that the web management page jump error in the screenshot occurs, unless the web management page jump error in the screenshot is first Turn off NCSI function.
shejialun wrote:
The bug I'm talking about is that when the device's LAN is working on subnet 192.168.1.0/24, it will not activate the windows 10 client's NSCI function, but when the device switches to subnet 10.0.0.0/24 subnet, it will activate the windows 10's NCSI function to the extent that the web management page jump error in the screenshot occurs, unless the web management page jump error in the screenshot is first Turn off NCSI function.
No Netgear router, in fact no Linux system, does participate in any way (certainly not active) with Windows NSCI. This happens only on your Windows system(s).
Theres a new beta version that you might try:
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
