I was just hit by this bug too, on my just finished Backup NAS.
Rebooting did not solve the issue.
I have just finished setting up my MJ11-EC1 backup NAS
Installed w. Dragonfish-24.04.2.3 , and upgraded to Dragonfish-24.04.2.5.
The system was installed on another subnet, and was working fine.
Now I moved it to the “permanent” subnet. And when booting on the new subnet, the system was “unresponsible”.
I could see that the NIC did a DHCP request, and got DHCP information handed over for the new subnet. The ip address from the new subnet was set/used.
Having a BMC (IPMI) on the MJ11 board, i opened the console , and grabbed a linux screen.
It was easy to verify that there was no default gateway set in the kernel routing table, making the system unresponding on anything but the current subnet.
My magement PC isn’t on the same subnet as the NAS, so that’s why the system was unresponsible to me.
The fix was “easy” for me …
Via the BMC console i selected option 2 : Configure Network Settings.
And immediately i saw that the current :
ipv4gateway : Reflected the OLD install subnet DHCP Info
nameserver1 : Reflected the OLD install subnet DHCP Info
I manually changed those to the correct values for the new subnet, and all as fine. The modified settings survived a shutdown/reboot too.
Weather this is a Bug or a “Feature” i have no idea … I lean towards BUG.
Bug description :
On Dragonfish-24.04.2.5 - Using DHCP for network settings:
The DHCP def-gw and dns servers aren’t updated in the linux (scale) configs , if moving the unit to another subnet.
Guess: Dragonfish DHCP connect script doesn’t update the linux config, on “every” boot. Just on install.
Edit: Made a bug report - You’ve created “NAS-133114” issue