Lease files piling up in /var/lib/NetworkManager

greenjeans · Yesterday 21:14:02

So this seems like my own problem and not one with Devuan in general, so starting a new thread hoping maybe a network guru can help.

I have 3 partitions on my machine, sda1 is a Devuan Mate first installed in 2023, never modded or snapshotted or vuu-do'ed and it doesn't have this issue.

The other 2 partitions are Vuu-do, one a build partition for isos, the other a development partition, and they both suffer this issue.

A large build-up of old lease files for eth0 in /var/lib/NetworkManager, hundreds literally. System is generating a new one at every boot, and not deleting or overwriting the old one(s).

So far the only difference I have been able to find, is that sda1 has a keyfile for the interface in /etc/NetworkManager/system-connections, and the other 2 partitions do not have one. For some reason they aren't generating the keyfile, and i'm thinking this may be why there's a new lease file generated at every boot, because if the keyfile is present it just re-uses it without genning a new lease file?

A relevant section from Snapshot:

# Clear configs from /etc/network/interfaces, wicd and NetworkManager
# connman and netman, so they aren't stealthily included in the snapshot.
if [[ -z $netconfig_opt ]] ; then
	echo "# The loopback network interface
auto lo
iface lo inet loopback
" > "$work_dir"/myfs/etc/network/interfaces
	rm -f "$work_dir"/myfs/var/lib/wicd/configurations/*
	rm -f "$work_dir"/myfs/etc/wicd/wireless-settings.conf
[b]	rm -f "$work_dir"/myfs/etc/NetworkManager/system-connections/*[/b]
	rm -f "$work_dir"/myfs/etc/network/wifi/*
	rm -rf "$work_dir"/myfs/var/lib/connman/*

Which is very sensible and does explain why the system-connections folder is empty to start with, but doesn't explain why NM is not generating a new connection file once you've connected in a new install.

One other difference between the working and not-working systems is in /etc/network/interfaces, which in the working system reads:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

While in the non-working partitions reads:

auto lo
iface lo inet loopback

So the only difference is that source /etc/network/interfaces.d/* line, but I don't see how that would make a difference, there's nothing in interfaces.d on any of the partitions.

EDIT: Grasping at straws here, but another difference between the affected and not affected systems is iptables is installed along with the newer nftables in the working partition, the partitions having the issue only have nftables.

Last edited by greenjeans (Yesterday 22:23:09)

The officially official Devuan Forum!

#1 Yesterday 21:14:02

Lease files piling up in /var/lib/NetworkManager

Board footer