my RUT has been running well for several years on a remote site. It has supported a growing number of clients - now at about 390 clients. All low bandwidth.
Recently I’ve had the entire LAN drop out - all ethernet LAN connected clients lose connections to WAN. Devices like an onsite laptop that is both LAN and WLAN connected, drops the LAN but remains contactable via WLAN.
I can still contact the RUT via ZeroTier and RMS, in order to reboot.
Reboot resolves the issue, but it reoccurs within days.
The network.log still shows the 380-ish clients in the ARP table, but they are not contactable and they cannot reach the WAN.
The system.log is basically full of these " Resource temporarily unavailable" messages. Also lots of repeated DHCPdiscover/offer messages for a repeating handful of DHCP clients. See below.
I suspect that the problem may be so many connections
because this has occurred suddenly after adding the latest 10 clients.
Currently the RUT is peaking at 3225 TCP connections. Load over the same 15m period is 0.25.
My LAN architecture is Port based VLAN with approx 200 static clients on each VLAN (3 VLANS total) plus a handful of DHCP clients.
Appreciate any help diagnosing this!
Tue Mar 26 14:57:33 2024 daemon.info dnsmasq-dhcp[6809]: DHCPOFFER(br-lan) 10.0.0.226 fc:9c:98:17:74:19
Tue Mar 26 14:57:34 2024 daemon.err rms_mqtt[8995]: Level: 16, Log: Client 1114935689 received PUBCOMP (Mid: 4, RC:0)
Tue Mar 26 14:57:34 2024 daemon.err dnsmasq[6809]: failed to send packet: Resource temporarily unavailable
Tue Mar 26 14:57:35 2024 daemon.err dnsmasq[6809]: failed to send packet: Resource temporarily unavailable
Tue Mar 26 14:57:35 2024 daemon.err dnsmasq[6809]: failed to send packet: Resource temporarily unavailable
Tue Mar 26 14:57:35 2024 daemon.info dnsmasq-dhcp[6809]: DHCPDISCOVER(eth0.3) 10.0.2.228 fe:50:03:2c:67:3c
Tue Mar 26 14:57:35 2024 daemon.info dnsmasq-dhcp[6809]: DHCPOFFER(eth0.3) 10.0.2.228 fe:50:03:2c:67:3c
Tue Mar 26 14:57:37 2024 daemon.err dnsmasq[6809]: failed to send packet: Resource temporarily unavailable
Tue Mar 26 14:57:37 2024 daemon.info dnsmasq-dhcp[6809]: DHCPDISCOVER(br-lan) fc:9c:98:17:74:19
Tue Mar 26 14:57:37 2024 daemon.info dnsmasq-dhcp[6809]: DHCPOFFER(br-lan) 10.0.0.226 fc:9c:98:17:74:19
Tue Mar 26 14:57:38 2024 daemon.info dnsmasq-dhcp[6809]: DHCPDISCOVER(eth0.3) 10.0.2.228 fe:50:03:2c:67:3c
Tue Mar 26 14:57:38 2024 daemon.info dnsmasq-dhcp[6809]: DHCPOFFER(eth0.3) 10.0.2.228 fe:50:03:2c:67:3c
Tue Mar 26 14:57:40 2024 daemon.info dnsmasq-dhcp[6809]: DHCPDISCOVER(br-lan) fc:9c:98:17:74:19
Tue Mar 26 14:57:40 2024 daemon.info dnsmasq-dhcp[6809]: DHCPOFFER(br-lan) 10.0.0.226 fc:9c:98:17:74:19
Tue Mar 26 14:57:41 2024 daemon.err dnsmasq[6809]: failed to send packet: Resource temporarily unavailable
Tue Mar 26 14:57:42 2024 daemon.err dnsmasq[6809]: failed to send packet: Resource temporarily unavailable
Tue Mar 26 14:57:43 2024 daemon.err dnsmasq[6809]: failed to send packet: Resource temporarily unavailable
Tue Mar 26 14:57:44 2024 daemon.err dnsmasq[6809]: failed to send packet: Resource temporarily unavailable
Tue Mar 26 14:57:46 2024 daemon.err dnsmasq[6809]: failed to send packet: Resource temporarily unavailable
Tue Mar 26 14:57:46 2024 daemon.err dnsmasq[6809]: failed to send packet: Resource temporarily unavailable