INTL 3:770/1 3:770/3
REPLYADDR not@telling.you.invalid
REPLYTO 3:770/3.0 UUCP
MSGID: <66cbb981@news.ausics.net> 58b7aa80
REPLY: ebb2a67b
PID: SoupGate-Win32 v1.05
mm0fmf wrote:
> I have a Pi Zero W with a weird Wifi issue.
>
> The Pi runs an SSH gateway and is powered from a USB port on the router.
> It's been running faultlessly for about 2years now with a few tweaks to
> the standard setup to mount regularly written to files on a ramdisk to
> preserve the SDcard. The system reboots every 24hrs as a simple way of
> stopping the ramdisk filling up.
>
> After a new router was installed, this Pi has issues connecting to Wifi.
>
> Power it up and there's a 75% chance it will connect. If it doesn't
> removing and reapplying power makes it likely to connect. If you reboot
> it from the command line it fails to connect most times.
Perhaps not enough enthropy in /dev/random for wpa_supplicant to
work? I had that problem initialising the Pi Zero W's WiFi from
scratch via custom scripts on Linux, fixed by using Haveged to fill
the enthropy pool quicker. NetworkManager in Debian is the other
end of the spectrum so far as ways of setting WiFi up go though. It
probably already has that sorted out.
--
__ __
#_ < |\| |< _#
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 10/0 1 90/1 103/705 105/81 106/201 124/5016 129/305 153/757
SEEN-BY: 153/7715 218/0 1 601 700 840 870 930 220/70 221/1 6 360 226/17
SEEN-BY: 226/30 100 227/114 229/110 111 114 200 206 300 317 400 426
SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038
SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364
SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100
SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35
PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426
|
