Any problems switching from 192.168.1.1 to 192.168.0.1

:smileywink:

Follow up:

Set up was easy - having done it before with many routers - and the switch from 192.168.1.1. to xxx.xxx.0.1 was also easy - though it required logging back in under 192.168.0.1 because the app was looking for 1.1 . . .  once I figured out what it was trying to do I got back in. 

One hitch in the giddy up was that there were no separate 2.4 and 5ghz names - and I used my old name 5ghz name - when I discovred there were no separate names I realized I was going to have to reconnect the printers manually - the IP reservations were simple - I pulled the MAC addresses off the java app that Brother provides before I started the process. 

I have not develved into the instruction manual to see if I can separate the names for the two systems so I will have to reconnect the scanner / printer which is the one that is the pita - and also all my exterior security cameras that run off 2.4ghz only. 

Speeds are 400mbps on a 400ghz connection both wired and then wireless in the same room as the router [on a 400mbps connection from Spectrum]  - I have a ethernet hub in the attic and I wired backhauled the satellites - speeds are 400mbps in the rooms where the sats are - so I'm happy. . .

Glad you got it working well. 

Officially NG does not support separation of SSIDs on Orbi systems, thus you wont see this in the UI. Though if you really have to, others have found way to separate SSID names. Those have done this are a mixed bag of success and failure. I would recommend running the system with a single SSID name for a while tor see how it runs for you. I have been using single SSID name since Smart Connect first appeared back in 2012. Overall it works well. Some users are just not into change which is understandable. There are some issues with connecting new 2.4Ghz IoT devices to Orbi. 

NG has help with this by allowing users to disable the SSID on either frequency to help get the IoT devices connect. This is not a Orbi issue, this is a IoT mfr issue that is with there setup software requiring the setup phone or pad to be connected to the 2.4Ghz radio only. Mfrs fail to realized that dual band phones or pads can connect to either frequency which both radios on are the SAME network side of the fence. Why IoT Mfrs limit this in there software is unknown. 

Be sure to make a backup configuration to file for safe keeping. Saves time if a reset is needed. 

Enjoy. :smileywink:

it seems like my cameras and my Ring work fine by identifying the 2.4ghz section of the signal and running through it - so there is no need for me to split the systems -

Interesting the orbilogin.com does NOT identify the more recent firmware - its still two versions behind and does not recoginize a new firmware - thats likely a backroom problem at net gear.   If its working there is no reason to cause a problem! And contactng netgear will just cause confusion on their CS people - no one listens to what you are telling them and they have no way of fixing this issue  - they'll just send you standard answer number 4 and tell you to manually update - yeah-  I know how to do that-  not why I'm calling. 

Also - read my last post and we have a 400mbps connection not 400ghz - fat fingered that.  

---

comanchepilot wrote:

it seems like my cameras and my Ring work fine by identifying the 2.4ghz section of the signal and running through it - so there is no need for me to split the systems -

---

I think you have saved yourself from a future of frustration.

---

comanchepilot wrote:

Interesting the orbilogin.com does NOT identify the more recent firmware - its still two versions behind and does not recoginize a new firmware - thats likely a backroom problem at net gear.

---

It is frustrating that Netgear offers no explanation for this phenomenon.  My most "charitable" hypothsis is that (a) they see no urgency (i.e. security) reason to force this firmware if a person "has no problems", and (b) they would rather "wait and see" as people discover and install the new firmware manually.  If the early adopters discover significant issues, at least Netgear is not facing thousands of complaints that, "I did what you advised me to and now my system is broken!"

Glad it's working with out separation. As it should and does. Especially if you use the same SSID name and password from your old router. 

Ya the update mechanism is quirky to say the least. One reason why I manual update and apply FW my self. Sometimes it takes a while and you may see the update happen at a later time...

If your system is working for you. Keep it were it's at. Later on at somepoint or if you notice problems appearing, then maybe update yourself, factory reset and setup from scratch again. 

Besure to make a back up configuration to file for safe keeping. 

Enjoy. :smileywink:

---

comanchepilot wrote:

it seems like my cameras and my Ring work fine by identifying the 2.4ghz section of the signal and running through it - so there is no need for me to split the systems -

 

Interesting the orbilogin.com does NOT identify the more recent firmware - its still two versions behind and does not recoginize a new firmware - thats likely a backroom problem at net gear.   If its working there is no reason to cause a problem! And contactng netgear will just cause confusion on their CS people - no one listens to what you are telling them and they have no way of fixing this issue  - they'll just send you standard answer number 4 and tell you to manually update - yeah-  I know how to do that-  not why I'm calling. 

 

Also - read my last post and we have a 400mbps connection not 400ghz - fat fingered that.  

 

---