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,908 of 21,939   
   bp@www.zefox.net to The Natural Philosopher   
   Re: A bit more on Bookworm and WiFi prob   
   28 Oct 24 01:44:32   
   
   INTL 3:770/1 3:770/3   
   REPLYADDR bp@www.zefox.net   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  f3521820   
   REPLY:  a0038972   
   PID: SoupGate-Win32 v1.05   
   The Natural Philosopher  wrote:   
   > A power cut this a.m had my Pi zero W reconnecting to the  wrong wifi.   
   >   
   > Which forced me to delve into the depths of network manager as evinced   
   > by nmcli. Network manager is the new way to manage networks, and like   
   > systemd, its all changed for the sake of it   
   >   
   > You probably can edit the files directly - mine were in   
   > /etc/NetworkManager/system-connections, but it's safer to use nmcli tools   
   >   
   >   
   > You can set a priority if you have more than one wifi SSID.   
   >   
   > sudo nmcli c modify   connection.autoconnect-priority 1   
   >   
   > You can also force it to use 5Ghz or 2.4Ghz or let it decide   
   >   
   > sudo nmcli c modify  802-11-wireless.band "bg"   
   >   
   > or   
   >   
   > sudo nmcli c modify  802-11-wireless.band "a"   
   >   
   >   
   > "bg" is 2.4GHz, "a" is 5GHz.   
   >   
   > It may well be that bookworm has changed the implicit defaults in   
   > network manager.   
   >   
   > It is well worth dumping the connections with   
   >   
   > sudo nmcli connection show    
   >   
   > To work out what the connection names are, use   
   >   
   > sudo nmcli c show   
   >   
   > I think - but am not sure - that you can set more stuff through the   
   > command line than through the GUI interface to network manager   
   >   
   >   
      
   After a bit more fumbling two new wrinkles emerged. One was a report   
   of wifi being turned off by rfkill. This happened once before, and   
   re-setting the locale options seemed to fix it. This time re-establishing   
   the locale had no detectable effect.   
      
   After a bit more fumbling it appears that the wifi connects readily   
   when the wired ethernet is also connected. Maybe that's significant,   
   but exactly how isn't apparent to me.   
      
   Thanks for posting the hints on using nmcli!   
      
   bob prohaska   
      
   --- 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