Recently my router stopped giving out ip addresse and I think (but am not sure) this is because the filesystem has run out of space (and any leases files cannot be updated):
I was wondering if anyone can give me some advice on how I can go about working out what data I can clean up and where it located ?
df looks like:
$ df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 27.8M 27.8M 0 100% /
none 512.0K 0 512.0K 0% /dev
The majority of the space appears to be taken up in /usr:
The files in /usr/share/tor (geoip and geoip6) appear to be quite big - anyone know what they are ?
Also does anyone have any ideas on how I can help prevent this happening again ?
Is it possible to stick in a usb stick and use that as additional storage space ?
Joined: 16 Nov 2015 Posts: 6447 Location: UK, London, just across the river..
Posted: Sun Jan 21, 2024 13:13 Post subject: Re: How to free up file system space and stop it filling up
Shaggy1 wrote:
Recently my router stopped giving out ip addresse and I think (but am not sure) this is because the filesystem has run out of space...:
or your set up is bad and you went out of IP addresses...
if all wifi clients have lease time one day(for example)...and your dhcp range is too small, 16 or 32 or 64 hosts and you had lots of clients that come and go, than it will reserve all those IP and wont give more addresses until the DHCP daemon reset the lease table and build it again...i'll presume your reserved/static IP's also count...so set your DHCP daemon to 360min(home use) or what ever for a busy environment (like school or coffee) 30 to 60 min is fine...
I guess its very much "user/setup error" as my routers are 24/7 and never had such an issue... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Initially I also thought it was that I may have run out of leases, but in my conf file max leases is 56 and /tmp/dnsmasq.leases is empty.
As far as can tell there are nowhere near that many devices that might be connecting in the house (though I guess with kids you never know with kids).
Someone mentioned it might be that there is no space left, so that is what took me down the route of thinking it was a space issue. From the replies it looks like this not the case.
If it does reach the max number of leases does anyone know if there would be an indication somewhere that the max number of leases have been reached ?
And how to tell when/whether they are released ? Would I need to release them manually ?
(I do indeed also have 6 statically assigned addresses)
I have now taken the router off line so nothing is connected and have it next to my laptop so I can attempt to obtain a lease from a single machine.
I do not know much about dnsmasq and was wondering if someone could give me some advice on how I can try to debug the issue.
When I try to connect with wireless it does not manage to obtain a lease.
On trying to connect the system log output on my laptop looks like:
Code:
Feb 04 09:52:50 larrycotton-Latitude-E7440 gnome-shell[2915]: ../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function.
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2014] device (wlp2s0): Activation: starting connection 'lcwire2.4G_backup' (5b450634-cccc-441c-8470-abec2ced347f)
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2015] audit: op="connection-activate" uuid="5b450634-cccc-441c-8470-abec2ced347f" name="lcwire2.4G_backup" pid=2915 uid=1000 result="success"
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2017] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2022] manager: NetworkManager state is now CONNECTING
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2027] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2031] device (wlp2s0): Activation: (wifi) access point 'lcwire2.4G_backup' has security, but secrets are required.
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2032] device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2067] device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2072] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2077] device (wlp2s0): Activation: (wifi) connection 'lcwire2.4G_backup' has security, and secrets exist. No new secrets needed.
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2079] Config: added 'ssid' value 'lcwire2.4G_backup'
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2081] Config: added 'scan_ssid' value '1'
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2082] Config: added 'bgscan' value 'simple:30:-70:86400'
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2084] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2085] Config: added 'auth_alg' value 'OPEN'
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2085] Config: added 'psk' value '<hidden>'
Feb 04 09:52:57 larrycotton-Latitude-E7440 wpa_supplicant[866]: wlp2s0: SME: Trying to authenticate with b0:39:56:93:36:6c (SSID='lcwire2.4G_backup' freq=2462 MHz)
Feb 04 09:52:57 larrycotton-Latitude-E7440 kernel: wlp2s0: authenticate with b0:39:56:93:36:6c
Feb 04 09:52:57 larrycotton-Latitude-E7440 kernel: wlp2s0: send auth to b0:39:56:93:36:6c (try 1/3)
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2301] device (wlp2s0): supplicant interface state: disconnected -> authenticating
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2301] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> authenticating
Feb 04 09:52:57 larrycotton-Latitude-E7440 wpa_supplicant[866]: wlp2s0: Trying to associate with b0:39:56:93:36:6c (SSID='lcwire2.4G_backup' freq=2462 MHz)
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2313] device (wlp2s0): supplicant interface state: authenticating -> associating
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2313] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating
Feb 04 09:52:57 larrycotton-Latitude-E7440 kernel: wlp2s0: authenticated
Feb 04 09:52:57 larrycotton-Latitude-E7440 kernel: wlp2s0: associate with b0:39:56:93:36:6c (try 1/3)
Feb 04 09:52:57 larrycotton-Latitude-E7440 kernel: wlp2s0: RX AssocResp from b0:39:56:93:36:6c (capab=0x411 status=0 aid=1)
Feb 04 09:52:57 larrycotton-Latitude-E7440 wpa_supplicant[866]: wlp2s0: Associated with b0:39:56:93:36:6c
Feb 04 09:52:57 larrycotton-Latitude-E7440 wpa_supplicant[866]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Feb 04 09:52:57 larrycotton-Latitude-E7440 kernel: wlp2s0: associated
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2489] device (wlp2s0): supplicant interface state: associating -> 4-way handshake
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.2490] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> 4-way handshake
Feb 04 09:52:57 larrycotton-Latitude-E7440 wpa_supplicant[866]: wlp2s0: WPA: Key negotiation completed with b0:39:56:93:36:6c [PTK=CCMP GTK=CCMP]
Feb 04 09:52:57 larrycotton-Latitude-E7440 wpa_supplicant[866]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to b0:39:56:93:36:6c completed [id=0 id_str=]
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.3128] device (wlp2s0): supplicant interface state: 4-way handshake -> completed
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.3129] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "lcwire2.4G_backup"
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.3129] device (p2p-dev-wlp2s0): supplicant management interface state: 4-way handshake -> completed
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.3131] device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Feb 04 09:52:57 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040377.3138] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Feb 04 09:52:57 larrycotton-Latitude-E7440 avahi-daemon[823]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::986f:6cb4:950c:5760.
Feb 04 09:52:57 larrycotton-Latitude-E7440 avahi-daemon[823]: New relevant interface wlp2s0.IPv6 for mDNS.
Feb 04 09:52:57 larrycotton-Latitude-E7440 avahi-daemon[823]: Registering new address record for fe80::986f:6cb4:950c:5760 on wlp2s0.*.
Feb 04 09:52:57 larrycotton-Latitude-E7440 wpa_supplicant[866]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-19 noise=9999 txrate=144400
Feb 04 09:52:58 larrycotton-Latitude-E7440 wpa_supplicant[866]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-5 noise=9999 txrate=144400
Feb 04 09:53:00 larrycotton-Latitude-E7440 wpa_supplicant[866]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-5 noise=9999 txrate=144400
Feb 04 09:53:12 larrycotton-Latitude-E7440 wpa_supplicant[866]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-5 noise=9999 txrate=144400
Feb 04 09:53:42 larrycotton-Latitude-E7440 NetworkManager[832]: <warn> [1707040422.2930] dhcp4 (wlp2s0): request timed out
Feb 04 09:53:42 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040422.2930] dhcp4 (wlp2s0): state changed unknown -> timeout
Feb 04 09:53:42 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040422.2932] device (wlp2s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Feb 04 09:53:42 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040422.2944] manager: NetworkManager state is now CONNECTED_LOCAL
Feb 04 09:53:42 larrycotton-Latitude-E7440 NetworkManager[832]: <warn> [1707040422.2981] device (wlp2s0): Activation: failed for connection 'lcwire2.4G_backup'
Feb 04 09:53:42 larrycotton-Latitude-E7440 avahi-daemon[823]: Withdrawing address record for fe80::986f:6cb4:950c:5760 on wlp2s0.
Feb 04 09:53:42 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040422.2987] device (wlp2s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Feb 04 09:53:42 larrycotton-Latitude-E7440 avahi-daemon[823]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::986f:6cb4:950c:5760.
Feb 04 09:53:42 larrycotton-Latitude-E7440 avahi-daemon[823]: Interface wlp2s0.IPv6 no longer relevant for mDNS.
Feb 04 09:53:42 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040422.3215] dhcp4 (wlp2s0): canceled DHCP transaction
Feb 04 09:53:42 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040422.3215] dhcp4 (wlp2s0): state changed timeout -> done
Feb 04 09:53:42 larrycotton-Latitude-E7440 kernel: wlp2s0: deauthenticating from b0:39:56:93:36:6c by local choice (Reason: 3=DEAUTH_LEAVING)
Feb 04 09:53:42 larrycotton-Latitude-E7440 wpa_supplicant[866]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=b0:39:56:93:36:6c reason=3 locally_generated=1
Feb 04 09:53:42 larrycotton-Latitude-E7440 NetworkManager[832]: <warn> [1707040422.4392] sup-iface[0x55c1e7b69900,wlp2s0]: connection disconnected (reason -3)
Feb 04 09:53:42 larrycotton-Latitude-E7440 wpa_supplicant[866]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Feb 04 09:53:42 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040422.4408] device (wlp2s0): supplicant interface state: completed -> disconnected
Feb 04 09:53:42 larrycotton-Latitude-E7440 NetworkManager[832]: <info> [1707040422.4409] device (p2p-dev-wlp2s0): supplicant management interface state: completed -> disconnected
As mentioned I do not know anything about dnsmasq, so do not really know what I should expect to see, but when I montior for dhcp messages using tcpdump on the wireless interface on the laptop I see only this:
Code:
$ tcpdump -i wlp2s0 udp port 67 and port 68
10:33:34.317050 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 80:86:f2:c5:85:32 (oui Unknown), length 304
10:33:36.545507 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 80:86:f2:c5:85:32 (oui Unknown), length 304
10:33:41.194650 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 80:86:f2:c5:85:32 (oui Unknown), length 304
10:33:49.382907 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 80:86:f2:c5:85:32 (oui Unknown), length 304
10:34:06.332556 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 80:86:f2:c5:85:32 (oui Unknown), length 304
So it looks like I never get a reply from the router
As a comprarison when I connect to my (now) main router which is an identical r7800 (with what I think is an identical configuration) I do see the received reply.
(I had thought I would also see discover/offer messages which I don't)
Code:
$ tcpdump -i wlp2s0 udp port 67 and port 68
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlp2s0, link-type EN10MB (Ethernet), capture size 262144 bytes
10:28:38.767859 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 80:86:f2:c5:85:32 (oui Unknown), length 304
10:28:38.776829 IP xx.xx.xx.1.bootps > xx.xx.xx.121.bootpc: BOOTP/DHCP, Reply, length 307
10:28:38.776945 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 80:86:f2:c5:85:32 (oui Unknown), length 316
10:28:38.836868 IP xx.xx.xx.1.bootps > xx.xx.xx.121.bootpc: BOOTP/DHCP, Reply, length 335
$ brctl show
bridge name bridge id STP enabled interfaces
br0 8000.b03956933669 no eth1
wlan0
wlan1
Code:
$ iwconfig
wlan1 IEEE 802.11 Mode:Master
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
oet1 no wireless extensions.
wlan0 IEEE 802.11 Mode:Master
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
eth0 no wireless extensions.
br0 no wireless extensions.
teql0 no wireless extensions.
lo no wireless extensions.
eth1 no wireless exten
sions.
> A client with MAC Address 80:86:f2:c5:85:32 is trying to get an address with the BOOTP Protocol. This is the protocol that preceded DHCP back in 1985.
Yes, I believe that's my laptop requesting an address
