Mellon wrote: > It may be worth remembering that packet loss is not ALWAYS a result of a > network malfunction. > > For example, if the device you are pinging is already working hard > trying to do something else, that could be a reason for it to drop the > ping request, rather than the ping request not making it there, or back, > on the network. I'm not sure if there is any way to check CPU load, or > any other process which may cause it to not respond promptly in Picore? > > Is the ping response you provided an example of the Wifi going down > regularly, or does it run like this and then you get nothing but Request > timed out?
It's also worth remembering that the whole Pi range is very cheap and quality control is, as a result, patchy. Another apparently identical Pi Zero-W may work perfectly. Jim https://jukeradio.double6.net VB2.4[/B] STORAGE *QNAP TS419P (NFS) [B]Living Room* Joggler & Pi4/Khadas -> Onkyo TXNR686 -> Celestion F20s *Office* Joggler & Pi3 -> Denon RCD N8 -> Celestion F10s *Dining Room* SB Radio *Bedroom (Bedside)* Pi Zero+DAC ->ToppingTP21 ->AKG Headphones *Bedroom (TV) & Bathroom* SB Touch ->Denon AVR ->Mordaunt Short M10s + Kef ceiling speakers *Guest Room* Joggler > Topping Amp -> Wharfedale Modus Cubes ------------------------------------------------------------------------ d6jg's Profile: http://forums.slimdevices.com/member.php?userid=44051 View this thread: http://forums.slimdevices.com/showthread.php?t=115095 _______________________________________________ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
