Unable to reset network

Insight & Feedback
1

I am trying to revert some network changes I made through the UI following the instructions linked from the UI (Reset Network Settings | Zimaspace Docs) but they appear to not work? Per below the USB drive is formatted exfat and AFAICT I have the right file (_ResetNetwork in the root directory with no contents).

root@ZimaBoard2:/root ➜ # mount|grep -i usb
/dev/sdb1 on /media/sda1-usb-USB_SanDisk_3.2 type exfat (rw,relatime,fmask=0022,dmask=0022,iocharset=utf8,errors=remount-ro)
/dev/sdb1 on /DATA/.media/sda1-usb-USB_SanDisk_3.2 type exfat (rw,relatime,fmask=0022,dmask=0022,iocharset=utf8,errors=remount-ro)
/dev/sdb1 on /var/lib/casaos_data/.media/sda1-usb-USB_SanDisk_3.2 type exfat (rw,relatime,fmask=0022,dmask=0022,iocharset=utf8,errors=remount-ro)
root@ZimaBoard2:/root ➜ # ls -l /media/sda1-usb-USB_SanDisk_3.2/_ResetNetwork
-rwxr-xr-x 1 root root 0 Jun  2 05:34 /media/sda1-usb-USB_SanDisk_3.2/_ResetNetwork
root@ZimaBoard2:/root ➜ #
2

FWIW it seems it might have worked but the UI didn’t update, hard to say since I am not an expert at reading nmcli output, but that seems to say both NICs are back to default. Damn annoying about the strange device names in nmcli though.

3

Looks like you created the reset file correctly.

The official reset method says the USB should be exFAT, the file should be named exactly _ResetNetwork, it should be empty, and one sign of success is that the file gets removed from the USB after ZimaOS processes it. The other sign is that the IP/network state changes.

In your output, the file is still present:

/media/sda1-usb-USB_SanDisk_3.2/_ResetNetwork

So I would not treat that as 100% confirmed yet, even if nmcli looks like the NICs are back to default.

Maybe check these non-destructive outputs and post them here:

nmcli device status

nmcli connection show

ip addr

Also agree about the strange nmcli device names. It makes it harder than it needs to be to confirm what actually changed from the UI.

4

Thanks, much appreciated.

I would dump those but I’m currently experimenting with ProxMox (on a separate NVMe drive). IIRC they were blank / default which is why I add the message that things seemed to have actually been reset despite the UI saying otherwise.