I’ve just created a really basic network running on the default 192.168.1.x subnet -
Route10
A Proxmox host running Control in a container
A MacBook plugged into the Route10
Connected to the internet via our ISP’s modem.
All the devices worked OK. Although I did have to manually add the local ddns link to the Route10. All was working. I then thought I’d change to the 10.x.x.x subnet - no good reason just because.
All the devices picked up new IP’s in the new subnet. I could visit the local IP for the Route10 (told me it was already adopted) and for the Controller (told me to use the ddns link). I go to the local ddns link - nothing. It just spins and spins and the page never opens. I ended up resetting the Route10 to get back onto the 192.168.1.x subnet and the local ddns link started working again.
I did try adding the link to my MacBook’s hosts file but that didn’t work either.
Am I missing something obvious here? I’ll probably just stick to the default subnet for now anyway as it’ll probably be safer in case I have to reset again in the future.
Since you’re running in a self-hosted environment, have you dropped to the container env cli and run the system updates from there? I’m curious if the controller is just behind a version or two.
Hi Josh. I did run an apt update/upgrade within the container (I’m assuming that’s all that is required) and I also checked for updates in the Control GUI. All of that was before I changed the subnet to 10.x.x.x.
I had another go at this today. Powered everything up, everything was on the 10.x.x.x subnet and the local ddns was working. The controller was, and still is, on the latest version when I made the subnet change a couple of days ago. So I’m pleased to be able to say the link is working.
I think there was some confusion on my end as well. I started with the Route 10 on the default subnet (192.168.1.1), changed it to (10.x.x.x), the local ddns link then didn’t work but the Route10 and other devices all had 10.x.x.x IP’s. I reset the Route10 by holding down the reset button and the devices moved back to the 192.168.x.x subnet. Somewhere along the line when I added the Route10 back into the controller it started using the 10.x.x.x subnet again as I didn’t realise it would pick up the settings I had changed before resetting it.
Still, somehow I got to a working network on the subnet I had originally intended to use!
