- Minor
Slightly convoluted, but effectively I did a 71.2 - > 7.1.3 upgrade and had issues with connectivity (no web ui accessible from the local network), so rolled back to 7.1.2 (using USB creator tool) and whilst I had connectivity back to the web UI, had issues with dockers
Logs showed the container couldn't find the network ID
All br0.x VLANs where missing in the drop down list when editing a container and 'docker network list' showed they indeed did not exist.
I removed and re-added all VLANs, keeping the same Docker settings for those (IP ranges, DHCP Pools etc)
This still didn't work
I then found posts on here about the 'non standard' CIDR for DHCP address pools on VLANs, and I was using x.x.x.224/28 which is a valid CIDR subnet, but just set that to x.x.x.0/28 anyway, restarted everything and all the br0.x vlans reappeared.. I reset each container to the corresponding vlan br0 and all containers started fine.
I then noticed that my old docker config had vlans defined such as 192.168.0.1/24, but now, in both 7.1.2 and 7.1.3 I can only select CIDR subnet masks of 25-30..
Anyway, with it largely 'working', I re-upgraded to 7.1.3 on the basis I thought it might have been my CIDR DHCP pools on the vlans..
And on reboot to 7.1.3, even though the docker/vm manager is not enabled, just starting the array causes connectivity issues
ifconfig shows br0 is up with the correct static IP. eth0 is also present and shows no issues
wget {server ip} from the command line will get index.html, so that's working
The array is up (disks are mounted and can browse the shared folders from the command line)
I've attached pre array start and post array start diagnostics files if that helps in anyway..
I might have to revert back to 7.1.2 again, the only oddity is those VLAN subnet masks being limited to 25-30 and obviously I'd like to get to the bottom of this as my install is a few years old now, so might have some unwanted baggage that needs sorting out.
nas-diagnostics-20250606-1034.zip nas-diagnostics-20250606-1030.zip