So I am thinking of changing my router (I am changing my ISP and want a new separate router as well.)
My current router (provided by my ISP) uses 10.0.0.x for devices. My Home Assistant is running on an intel NUC in a Proxmox VM. I will be purchasing a separate router beyond my ISP router this time. The likely result will be something that uses 192.168.0.x or something along those lines. I hardwire my NUC directly to my router via network cable.
Not ever having to be concerned with IP addresses - I am worried with respect to what I might end up having happen. I don’t want to start something and then end up locked out my device. I only have access to my current router thought the App they provide - My router was likely used prior and the password that was set they cannot seem to reset it. - so I can see the IP address of every device, but I can not make a lot of changes to things. Part of the reason why I want to leave among others.
So, I am worried about whether this will affect Nabu Casa and local access to home assistant. Most of my devices are zwave and zigbee, so the few wifi devices I can reconfigure if necessary, but I would prefer something seamless.
Thanks,
Steve
Hi,
I don’t think your problem is in what router to buy, The question is how skilled you are with setting up your home network from scratch. Most of devices (routers) comes with default IP address preassigned, which often is 192.168.0.x or 192.168.1.x etc. Furthermore, they by default are set up to use DHCP, which means what ever you plug into the router it will be assigned a dynamic IP address (from that IP address range 192.168.0.x/24). I presume, that your installation of PROXMOX VE has static ip, and most likely all the VMs and LXCs in it have the static IP addresses assigned as well ( IP range 10.0.0.x/24). So, it is obvious that simple “re-plugging” of the network cable to new router simply won’t work. The simplest solution here is, when you buy a new router change the default IP address on new router from 192.168.x…x to 10.0.0.x and you can leave the DHCP enabled (that might work).
The other option for you would be to buy a router which allows you to set up multiple VLANs. This way you can set up one wlan (network) for home use (pc, laptop, wifi etc.). This network can be set up with IP range 192.168.1.x/24. Than setup separate VLAN for your IoT (HomeAssistant) network (HA, Zgbee, zwave etc.) this network can have different IP range (192.168.100.x/24 or 10.0.0.x/24). This solution has some security implications as the IoT network would be separated from your Home (main) network. For the devices in IoT network I would prefer to use a static IP (Home Assistant, Proxmox VE, maybe even for the switches etc.). For the devices in Home network the DHCP would be fine. In order to manage the IoT devices from the Home network a further setup of the firewall rules would be required.
At first it’s absolutely your choice which subnets you declare and use.
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
Let me give some hints for doing that
Don’t make your subnets too small.
think about network segregration (e.g you dont want to have your IOT Network included in your normal LAN)
think about a good firewall behind your ISP router
think about WiFis (different SSIDs(subnets) for e.g Surfing, Guests, IOT Network, …)
There are several nice hardware platforms where you can run pfsense on it. This is pretty awesome. Like having 4+ Gbit Ports on a small device where you can install pfsense. You can play this even further, when you connect a standalone AccessPoint to this. So that means everything can be filtered. You could assign different VLANs on one Port and connect the WiFi AP to that. Like with vlan1(your surfnet) 10.0.1.0/24, vlan2(iOT DMZ) 10.0.2.0/24, …
With a setup like that you will be likely +100$/€ more than you pay for a good other new router. So for the pfesense hardware + a dedicated AP.