home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   RBERRYPI      Support for the Raspberry Pi device      21,939 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 20,957 of 21,939   
   druck to The Natural Philosopher   
   Re: Wifi error log for Bookworm?   
   31 Oct 24 21:54:40   
   
   INTL 3:770/1 3:770/3   
   REPLYADDR news@druck.org.uk   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  85330ddc   
   REPLY:  1842e3a5   
   PID: SoupGate-Win32 v1.05   
   On 31/10/2024 09:46, The Natural Philosopher wrote:   
   > On 30/10/2024 21:24, druck wrote:   
   >> On 29/10/2024 21:08, Lawrence D'Oliveiro wrote:   
   >>> On Tue, 29 Oct 2024 20:28:40 +0000, druck wrote:   
   >>>   
   >>>> Quite often my Linux Laptops which use Network Manager decide   
   >>>> they would like to try WiFi networks other than the one I've chosen,   
   >>>> that's easily fixed via the gui, but not what you want on headless   
   >>>> systems.   
   >>>   
   >>> You could use nmcli to control it.   
   >>   
   >> If you can log in to a headless system which isn't connecting to the   
   >> Wifi.   
   >>   
   > Well at least all headless Pis will run a console session via some form   
   > of USB keyboard and HDMI screen. You wont need a mouse so one USB port   
   > is enough   
   >   
   > That what I have used when faced with loss of of connectivity.   
      
   Yes, I'm sure I could drag a monitor and keyboard up to the attic, or   
   down to the shed. However, it's easier in most situations to bring the   
   Pi back to the monitor and keyboard to sort it out.   
      
   But the point is; with the previous DHCPCD/WPAsuplicant the selection of   
   the WiFi network was immutable. With the hardware watchdog set to reboot   
   on crashes, if you couldn't connect to the Pi it was more likely the AP   
   wasn't working.   
      
   However, when using Network Manager, it sometimes decides to try a   
   different network, leaving a remote headless Pi stuffed. Whilst all my   
   'desktop/media' Pi's (connected to monitors and keyboards) are on   
   Bookworm, all the headless ones are remaining on Bullseye for the time   
   being.   
      
   ---druck   
      
   --- 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 128/187 129/305   
   SEEN-BY: 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1 6 360   
   SEEN-BY: 226/17 30 100 227/114 229/110 111 114 200 206 300 317 400   
   SEEN-BY: 229/426 428 470 550 616 664 700 240/1120 266/512 267/800   
   SEEN-BY: 282/1038 291/111 292/854 301/1 113 812 310/31 320/219 322/757   
   SEEN-BY: 335/364 341/66 342/200 396/45 460/58 633/280 712/848 770/1   
   SEEN-BY: 770/3 100 330 340 772/210 220 230 5020/400 1042 5075/35   
   PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca