NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
OldPilot2
Jun 05, 2020Aspirant
CM2200 on 192.168.100.1
I just bought a CM1100 and am extremely annoyed to find that its IP address is fixed at 192.168.100.1. The network I am installing it on uses the 192.168.2.xxx subnet, which means that the cable mod...
OldPilot2
Jun 06, 2020Aspirant
I am replacing a DSL modem/WAP/router with the CM2200 and a Linksys WAP/router. Today or tomorrow. I am using 192.168.2.xx. I am used to setting up my networks so I have access to my system boxes without a lot of fooling around. For example, the DSL box is at 192.168.2.251. I have that IP bookmarked and it is a simple matter of clicking the bookmark to get access to the box. I also have bookmarks for the port 80 interfaces to my NAS boxes. I want to have the same capability with the CM2200. Quite simple, actually.
I actually do know a little bit about this. I have been taking care of my home and business networks as a survival skill since Netware 2.x. I have even (gasp!) downloaded the manuals for the new boxes. Hassling with networks does not bring me joy; I do enough to get by and then I stop.
antinode
Jun 06, 2020Guru
> [...] I want to have the same capability with the CM2200. Quite
> simple, actually.
Yes, it is. Make a new bookmark for "192.168.100.1". When you use
that (special) address in your web browser, your (unspecified) "a
Linksys WAP/router" will see that address, notice that it's not on its
own LAN, and send it off toward your ISP. That is, to the CM1100, which
will intercept it, and respond appropriately. There's no need to do
anything different/special on your ("192.168.2.*") LAN to make that
work.
> [...] I have even (gasp!) downloaded the manuals for the new boxes.
> [...]
Did you see anything in any of them which suggested (let alone
demanded) that you "reconfigure [your] network to 1.92.168.100.xxx !"?
> [...] I do enough to get by and then I stop.
That's fine, if you know where "enough" ends.
> Don't go looking for trouble where there is none?
Still my advice.