NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi & the new Roomba i7+ connectivity
(I apologize for the repost. There was some sort of techinical error with my original post.) We recently purchased a Roomba i7+. We could not get it to connect to Roomba's servers to update it's s...
Yes if you had a modem/router combo before and it wasn't bridged, the Orbi will re-configure for 10. address pool. Since you have the newer SB series modem only, I presume you haven't every reset the Orbi thus keeping the 10 address pool. This is fine. It could be possible that maybe if you have not done a reset on the Orbi since, then maybe you can do this as a last resort.
Yes you set up the DMZ for the 3700 correctly. I was hoping this would help avoid any issues between the Orbi and Roomba however someting seems to be keeping the Roomba from fully connecting. It's possible there is some port issue or someting on Orbi thats stopping it.
Yes you'll see other wired devices on the 3700 as it's connected client app is searching was connected to it's LAN port thus seeing other devices stemming from the Orbi thru the 3700. This is expected.
If you decide to do the factory reset on the Orbi, go ahead and turn OFF the 3700 and Roomba for now. Set up the Orbi router from scratch, walk thru the setup wizard. This time you'll get a 192.168.1.1 on the router, You might first test the Roomba to see if it connects thru the router first. Then try setting WPA to disable temporarily. If the Roomba still does not connect fully with WPA disabled and it's services don't appear, then Roomba and NG need to review this and hopefully collaborate and find a fix. Be sure to re-enable WPA2 and AES after testing the Roomba.
I am going to describe what I did, and hopefully you can tell me if I did it correctly. I am far from great at this stuff, so I rely on online tutorials.
-I already had different SSID's set up for both routers. I ensured all were on different channels.
-In Orbi, under Advanced>Setup>LAN setup, I changed the Starting and Ending IP address range from 10.0.0.2-10.0.0.254 to 10.0.0.2-10.0.0.250, because something I read said to manually set up an AP, you had to give the AP router an IP address within the same subnet, but outside of the DHCP range of the main router.
-on the 3700, under Advanced>LAN Setup, I entered 10.0.0.254. I turned off UPnP, then I unchecked "Use Router as DHCP Server."
-I then connected a LAN port on the Orbi to a LAN port on the 3700.
What I am seeing now:
-I can successfully connect to the 3700's SSID's, with a working internet connection. I connected my phone and the Roomba to it.
-My phone and the Roomba are connected to the 3700's SSID, but in the Roomba app and on my phone, they show they are connected to Orbi's IP address.
-In Orbi under attached devices, the 3700, the Roomba and my phone are all showing up as WIRED devices connected to the Orbi Router.
The issue with my Roomba still exists.
Let me know if I did something incorrectly.
Yes great work on the 3700. you have it working.
Odd though that the Orbi is using 10. address scheme though, default is 192.168.1...Well if it's working don't bother this.
Lets try adding the IP address for the 3700 in to the Orbi routers DMZ and save settings, reboot the router and 3700 and Roombas.
Devices that are connected to the 3700 will show up as wired devices since the 3700 is actually a wired device connected to the Orbi router, so this is expected and ok.
Hoping this will help. I would recommend that you contact the Mfr of Roomba and give them this thread and see if they have any input. If ALL others devices connect and working with the Orbi and the Roomba is the only device having problems, Both Rooma and NG will need to have a review of this.
Thanks for confirming that I did the AP setup correctly.
The Orbi's IP as always been 10 for us. We have owned our fair share of routers, and it is a first for us. Back when we first got it, we used it with an modem/router combo from AT&T (fiber network.) Originally, we did not have the AT&T's router disabled. Maybe that has something to do with it? No clue! (We are currently using Cox's Gigablast service in a new state, as we had moved.)
Did I do this correctly? I went to ADVANCED>Setup>WAN Setup, clicked "Enable Default DMZ Server," and then entered the 3700's IP address. Then I reset everything. The issue still persists. Even if it did work, what kind of security risk is there for having the 3700 in the Orbi's DMZ?In the 3700's attached devices list, there are 9 devices now showing on the WIRED list, and then my phone and the Roomba in the Wireless.The Orbi Router and the two satellites are 3 of the 9 devices on the wired list. (Some were showing before I made the DMZ change.)
I have been in touch with iRobot's support for a few weeks now. Over the weekend, I sent them a message letting them know that the 3700 worked, so that means there is an issue between Orbi and Roomba. They just responded suggesting that I check for a firmware update on the Orbi. That was one of the first things I had tried. :smileylol: I will go ahead and link them with this thread, too.
Thank you so much for your help on this. I really appreciate it!
FURRYe38 wrote:
Yes great work on the 3700. you have it working.
Odd though that the Orbi is using 10. address scheme though, default is 192.168.1...Well if it's working don't bother this.
Lets try adding the IP address for the 3700 in to the Orbi routers DMZ and save settings, reboot the router and 3700 and Roombas.
Devices that are connected to the 3700 will show up as wired devices since the 3700 is actually a wired device connected to the Orbi router, so this is expected and ok.
Hoping this will help. I would recommend that you contact the Mfr of Roomba and give them this thread and see if they have any input. If ALL others devices connect and working with the Orbi and the Roomba is the only device having problems, Both Rooma and NG will need to have a review of this.
Yes if you had a modem/router combo before and it wasn't bridged, the Orbi will re-configure for 10. address pool. Since you have the newer SB series modem only, I presume you haven't every reset the Orbi thus keeping the 10 address pool. This is fine. It could be possible that maybe if you have not done a reset on the Orbi since, then maybe you can do this as a last resort.
Yes you set up the DMZ for the 3700 correctly. I was hoping this would help avoid any issues between the Orbi and Roomba however someting seems to be keeping the Roomba from fully connecting. It's possible there is some port issue or someting on Orbi thats stopping it.
Yes you'll see other wired devices on the 3700 as it's connected client app is searching was connected to it's LAN port thus seeing other devices stemming from the Orbi thru the 3700. This is expected.
If you decide to do the factory reset on the Orbi, go ahead and turn OFF the 3700 and Roomba for now. Set up the Orbi router from scratch, walk thru the setup wizard. This time you'll get a 192.168.1.1 on the router, You might first test the Roomba to see if it connects thru the router first. Then try setting WPA to disable temporarily. If the Roomba still does not connect fully with WPA disabled and it's services don't appear, then Roomba and NG need to review this and hopefully collaborate and find a fix. Be sure to re-enable WPA2 and AES after testing the Roomba.
That makes sense. No, we didn't do any sort of factory reset on the Orbi when we moved, or after I had figured out that having two routers was causing our double NAT. I do like the 10's for its simplistic look, though. lol Are there any disadvantages to the 10's? If I do do a factory reset and it gives me the ol' 192, can I manually switch it back to 10's if I want? :smileylol:
It is sounding like a full reset may be necessary. I don't think it should be too big of a deal other than having to rename a few things. UPnP has been working pretty well, for the most part, so we don't even have anything port forwarded anymore.