NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
mtiede
Dec 29, 2022Tutor
Should I be worried about my C7000v2 modem/router?
I wanted to have Spectrum update the modem/router. (I think previously Time Warner did at least one update) But now Spectrum (who acquired Time Warner) just says, "We don't update customer equip...
michaelkenward
Dec 30, 2022Guru - Experienced User
FURRYe38 wrote:
Only IP address that would be accessible is 192.168.100.1 thats the modems IP address for accessing that side of the units web page and when in modem model as well. Nothing else would be coming from the modem in modem mode.
That was my guess.
I didn't step in because I read the manual, which was misleading! (I suspect that mtiede did the same thing.) There I read:
"When your modem router is in bridge mode, use http://192.168.0.1 to
log in to your modem router."
It is only by reading earlier messages here, that I knew that the manual can be misleading. And not for the first time.
That address is, of course, the IP address of the device in modem/router mode.
Manuals for some another cable modem/router does list "http://192.168.100.1".
mtiede
Dec 31, 2022Tutor
I tried to go to 192.168.100.1 today. I see that my new router blocked that access of that address.
"ET POLICY Reserved Internal IP Traffic"
So I allowed it, and I was able to login to the old Netgear modem/router.
I see the modem is active and the wifi is turned off.
And I can see how to turn it back into modem/router mode if I wanted to do that.
And since I see that the new router saw the traffic where I logged into the old modem/router, I'm back to the original question again. Why was the modem apparently trying to get DNS information using the 192.168.100.10 address? Why would it get DNS information at all?
- mtiedeJan 02, 2023Tutor
I happened to get another Surface Pro 9 and tried the same install steps I did with the first one. This time I did not get the 192.168.100.10 attempted access. So I'm back to not knowing why apparently the disabled router was trying to get dns information.