I’ve got three RPis here running DietPi and Roon Bridge. Two of them work fine, and they are connected via Ethernet cabling. The third RPi uses WiFi, and it seems that after 24 hours or so, the WiFi connection disappears. I need to power cycle the RPi, and then it’s up and running again.
I say “after 24 hours or so” because I’ll be using the RPi one day (it drives my headphones in Roon), but when I come to use it again the next day, the RPi will have disappeared from Roon because the WiFi has gone (I can’t ping the RPi or PuTTY into it). So I have to power cycle the RPi to get it back again.
This behaviour has existed for at least the last few upgrades of DietPi (Roon shows I’m currently on Linux 4.9.27-v7+).
Is anyone else seeing this? It’s certainly not a showstopper, just a minor irritant, but I would like to get to the bottom of it. If no-one else is seeing it, I’ll try switching to the IQaudIO Roon Ready image (the RPi has an IQaudIO DAC+) to see if that makes a difference.
Good thought. It might well be that. The DHCP server I have running in the home network does indeed have a lease expiry time of 24 hours. All the other devices in the network seem to be able to renew their leases without a problem, but this RPi perhaps has an issue?
I’ve had my RPi 3 configured for a static IP for months (dietPi, IQaudIO HAT), and it seems to drop WiFi less than once per week (maybe much less). Overall, it seems more stable than even having the router assign a reserved fixed DHCP IP address to the Pi. For good measure, my RPi2 (dietPi, HifiBerry HAT) on Ethernet is also configured for static IP.
They are under /var/log
To my understanding DietPi does not log files like a normal system does… for issues like this it can be hard to catch… I can tell you for sure that there is other users using DietPi on a Pi 3 with no wifi issues (That I know of)
OK, thanks Dan. I’ll wait until it happens again, and then connect a keyboard/monitor to poke around.
The internal home network (and DHCP service) is provided by a Sophos UTM 9 setup running in a Windows VM. I have UTM 9 running because I have two internet connections (to two ISPs) running; one a slow ADSL connection, supplemented by a 4G connection. I expect that the UTM 9 will indeed be flushing connections upon lease expiry.
Change to use a different WiFi channel in the router. Normally people recommend using either 1, 6, or 11, but for experiment purpose look at any free WiFi analyzer app result on a smartphone, and try any channel between 1-11.
If you have a region setting in the router WiFi setup, make sure it is USA.
That’s not the issue.
a) I already use a channel that has no other traffic on it.
b) I’m living in the Dutch countryside, with no other strong WiFi signals in the neighbourhood.
c) None of the other WiFi devices in our household have this issue.