snapper undochange killed network access

English Applications
1

Hello All,

I explored the nice features of snapper for the first time. Just to try things out I wanted to ‘undo’ a deletion (by zypper rm ) of the xfce4 manager. I had installed it (zypper in) played with it for a moment, decided I didn’t want it anymore and removed it (zypper rm).

Following that step my network connection does not exist anymore.
Both eth0 and wlan0 show the infinite rotating little thingy in the network connection status popup.
Reboot doesn’t cure the problem.

Please suggest how I get my network back. (It was working before the snapper experiment)

Cheers,
Gert

2

To clarify.

Following zypper rm I did snapper undochange num…num. Expecting to see xfce
But instead io that the network disappeared and didn’t come back.

Thanks,
Gert

3

OK, cancel that. It was the router running out of internal disk.
(Just barely functioning but not able to establish a new connection to the laptop!)

BTW did anybody see stuff like this on an ASUS rt-ac68u router?

Jan  6 20:34:28 dnsmasq[259]: failed to allocate 124 bytes
Jan  6 20:34:28 dnsmasq-dhcp[259]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s)
Jan  6 20:34:28 dnsmasq-dhcp[259]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s)
Jan  6 20:34:29 dnsmasq-dhcp[259]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s)
Jan  6 20:34:33 dnsmasq[259]: failed to allocate 124 bytes
Jan  6 20:34:33 dnsmasq-dhcp[259]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s)
Jan  6 20:34:35 dnsmasq[259]: failed to allocate 124 bytes
Jan  6 20:34:35 dnsmasq-dhcp[259]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s)
Jan  6 20:34:37 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Jan  6 20:34:37 rc_service: check_watchdog 274:notify_rc restart_watchdog
Jan  6 20:34:39 dnsmasq-dhcp[259]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s)
Jan  6 20:34:40 dnsmasq[259]: failed to allocate 124 bytes
Jan  6 20:34:40 dnsmasq-dhcp[259]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s)
Jan  6 20:34:44 dnsmasq[259]: failed to allocate 124 bytes

Yes, I will ask the ASUS forum.

Cheers,
Gert

4

Haven’t seen it before, but for all DHCP leases the first likely solution that comes to mind is to
Stop the dnsmasq service

systemctl stop dnsmasq

Edit the file removing leases (maybe remove them all. DHCP normally creates a new lease as necessary)
Then start the dnsmasq service again.

TSU