Just to be clear, your hub is getting a reserved address from DHCP, as opposed to setting aside an address on the router and then manually setting the hub with that address? If the latter, the DNS addresses are not set, even though it appears that they are. You have to manually set them. Although this still wouldn't explain why your wired(?) PC cannot connect to the internet.
@ADiamond a couple of things come to mind...
Some orbi defaults to /23 instead of /24. Check that. It can cause issues
Is your orbi doing router functions so it's switch>>orbi>>isp's equipment ? If so is the ISP's equipment set to bridge or passthrough mode?
For giggles press the network reset button on the bottom of the hub for 7 seconds with a paperclip or toothpick. It will be the only round hole out of all the square ones. This resets the network only. Nothing else.
Do you have jumbo frames running anywhere on the network?
Are you using the factory power supply or a poe adapter?
1 Like
...and another thought. How many LAN devices do you have currently (Orbi limit is near 250)? Also could check to see if your hub is getting the same IP as another device (maybe your PC).
1 Like
when you go to go.hubitat.com, are you using http://go.hubitat.com/ vs https://go.hubitat.com/
1 Like
Things are a little different this morning, though I am still unable to connect and configure my C-8. I can connect to the internet with the C-8 connected to my switch. However, the Hubitat hub search is either unable to see the C-8, or it comes up with the wrong IP address for the C-8 during the search.
Using the go.hubitat.com configuration webpage, the hub has never been discovered on the basic discovery page, I have always needed to use the advanced discovery page.
A little more information about my home network: My Orbi router is configured to use a less common - but totally legit - reserved private LAN range: 172.16.0.0 thru 172.16.255.255. I can't use the typical 192.168.x.x home network addresses due to weird conflicts with my ISP modem.
I have a Verizon 5G Home Internet gateway for my ISP. The 5G gateway is configured to have all of its router-related functionality disabled (DHCP is disabled, all WiFi radios are disabled, etc.) The connection between the Orbi and the 5G gateway is a stateless autoconfigured IPv6 P2P connection on both ends, with IPv4 disabled on my Orbi, The gateway-Orbi P2P connection is set up as a passthru DMZ connection.
My goal was to make the 5G gateway as invisible to my Orbi and LAN as possible, and letting my Orbi be as unobstructed from the internet as possible (acting similar to an old cable modem). About the only functionality I have enabled on the VZW 5G gateway is its DDNS service, since my gateway switches IP addresses very frequently, sometimes multiple times in a day.
@jameslslate - The hub is getting all its network configuration from my Orbi router, the hub is not being configured manually at all.
@rlithgow1 - I have provided more information about my LAN configuration above, maybe it will help.
@thebearmay - I have about 25 devices on my LAN. Most are configured for the main LAN, some are auto-configured for the guest LAN (which the Orbi DHCP assigns in the 10.0.1.xxx range). The C-8 Hub is connected to the main LAN, and has been assigned an address of 172.16.1.17 by my Orbi.
@jschlote - I have tried http and https, no luck with either.
Since you are using a Class B network, you need to configure the Hubitat to use a Class B network mask.
Please read the thread linked to below for the issue you've run into, as well as one solution.
4 Likes
Well ... as if things weren't acting oddly enough ...
I seem to have my C-8 operational at this point, and hopefully reliably (TBD). I haven't done anything with regards to the Class B network subnet mask - yet.
When I started this thread last night, I couldn't connect to the C-8 through the go.hubitat.com webpage. I also couldn't connect to the C-8 directly by using its Orbi's assigned IP address.
As I was struggling with this issue this morning, and after my 3rd Orbi reboot, I was finally able to connect to the C-8 by going to its Orbi-assigned http://172.16.1.xxx IP address (go.hubitat.com still didn't connect). I went through the slightly different Hubitat setup screens, and I was able to download and install the latest C-8 firmware update.
I set up the C-8 to use WiFi, and I have set up a static IP address for the C-8 WiFi connection in the Orbi. I have bookmarked the http://172.16.1.yyy address for future easy access.
I have also enrolled my Z-Wave front door lock and started setting up Lock Code Manager.
Will I still need to make modifications to my C-8's configuration for the Class B network? While scanning the recommended thread, it seems like it could be a bit painful.
Maybe a silly question, but with so few devices in a home environment, why use the larger class B subnetting scheme?
6 Likes
@marktheknife - Nope, not a silly question, but I needed to use something other than the typical 192.168.x.x IP range to prevent IP address collisions with my cable modem in the past. When the Orbi router was configured in the 192.168.x.x IP range, there were times that I was forced to factory reset the Orbi router in order to regain access to the configuration pages again, even though the Orbi was fully functional otherwise. Neither Netgear nor the cable modem manufacturer could explain why it was happening, but Netgear recommended using a different IP range to resolve the issue, which it did.
I didn't want to use the larger 10.x.x.x range, although it was available.
Were you doing double NAT, because normally you get an routable (public) address from your ISP and then use a private address for your local network. If that is the case, you can still use 172.16.1.x with a subnet mask of 255.255.255.0 (Hubitat's default) and a default route of your router (probably 172.16.1.1).
7 Likes
This is what I would do. Just because there's an entire RFC1918 private Class B available, doesn't mean you can't just use one class C slice of it. You have a lot going on here. IPV6, 5G, double NAT. Once you have everything working I would suggest you document it like crazy. And because it is so complex I would make sure things are nailed down. The Class B/C thing is an example. If there's a mask mismatch someplace it might accidentally work for awhile, but then a random reboot somewhere breaks it. Understand every configuration choice. Verify it. Document it. Because later when you're either troubleshooting this or asking for help, a good diagram/document will be invaluable.
4 Likes
If you still can't get to your hub via this URL, you likely have a DNS issue and may need to manually configure DNS on your hub.
1 Like
So larger ranges aren't determined by scopes. 192, 172, 10. Are pretty much reserved scopes for private use. What's determines scope is your subnet. So you can set your subnet to /24 (255.255.255.0) regardless of what the scope is 192.168.1.x is. Otherwise with a /16 you're flat networking 65000 ip's which can be ok but can cause problems with some iot devices. I would shrink your subnet down to /24 and if you need more than 256 network devices then simply vlan off using the next one up while still maintaining a /24 for that subnet
5 Likes
It was probably double NAT'd, but they were also using the same ip address range of the OP's Orbi Router. That is pretty crappy of them to use the 192.168.1.x network space and screw anyone that uses a personal router. Almost all consumer home routers default to the 192.168.1.x network space when initially setup. Just starting their NATing at the 192.168.86.2.x network would of prevented for the OP is problems most likely.
Unfortunately this isn't as uncommon as you would hope. I had a friend that couldn't get his personal router working. Upon investigating it I found that his ISP was NATing his external ip and did the same thing. This was probably 20 years ago at that point. My ISP while I have had them changed from Public IP's for customers to a GNAT'd ip unless you pay a extra $5. It is a cash grab because of the thought they are running out of public IP's. If they would just switch everything to IPV6 this wouldn't be a issue, but it is a way to justify charging you for functionality of being to actually get back to your home from being remote.
As a few others have mentioned though just because the private range of the 172.16.x network space is a class B network doesn't mean you need to set your router to use the whole thing. It just means you could if you wanted to. If you just specify the third octet and then set your subnet mask to 255.255.255.0 then you will be back to a class c network and a limit of 253 hosts, or a typical consumer network.
5 Likes
Thanks, guys, for all the great suggestions and support!
Now that things are roughly stable, I typically save off my router configuration after major modification. I don't take Netgear router updates anymore. (Netgear Tech Support actually followed my suggestion and now make router updates optional after they bricked my Orbi - and probably many others - due to their forced firmware update policy)
I will follow the suggestion to set the router address range to a /24 subnet, and I suspect a number of devices are going to end up unhappy for a few days. I have run into subnet issues in the past with my current /16 subnet and got things resolved, so I expect I'll face a few temporary issues when I go in the other direction.
2 Likes
Just make a note of all your devices and do a DHCP reservation for your IOT devices. Let everything else be random.
3 Likes
I love it when you talk dirty... 
I actually gained some new networking info on this topic, very useful.
Seems to me @rlithgow1 should offer to drop by to troubleshoot. 
4 Likes
4 Likes
If most of your devices use DHCP and are npt set locally on the device then they will pull the updated subnet the next time they renew from the Router. Worst case scenerio would be you just need to reboot such a device. This is why i generally set everything in my router vs local config.
3 Likes
