| Deutsch English Français Italiano |
|
<vg2m5a$38u9q$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: The Natural Philosopher <tnp@invalid.invalid> Newsgroups: comp.sys.raspberry-pi Subject: Re: Wifi error log for Bookworm? Date: Fri, 1 Nov 2024 13:47:22 +0000 Organization: A little, after lunch Lines: 51 Message-ID: <vg2m5a$38u9q$1@dont-email.me> References: <vff1oh$30ljh$1@dont-email.me> <KOudndzl6uD98oD6nZ2dnZfqn_SdnZ2d@giganews.com> <vflpm5$gigb$1@dont-email.me> <vfm4ov$ifnc$1@dont-email.me> <vfo90b$11gf5$3@dont-email.me> <vfohs7$13j16$1@dont-email.me> <vfomlo$14f3e$1@dont-email.me> <vfrgho$1mkm5$1@dont-email.me> <vfrisv$1n56m$6@dont-email.me> <vfu85s$2ad65$3@dont-email.me> <vfvjmf$2khfc$7@dont-email.me> <vg0ub0$2rtar$1@dont-email.me> <vg2a88$36p2h$4@dont-email.me> <vg2ipp$383cp$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Fri, 01 Nov 2024 14:47:23 +0100 (CET) Injection-Info: dont-email.me; posting-host="04679a09dffba87dc666bf08829c5cf3"; logging-data="3438906"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19B5/E986sJBxqGuINLy3Xhu524niNjtt0=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:0nP0yZnapgSp8QZpf9b5JqJkjew= Content-Language: en-GB In-Reply-To: <vg2ipp$383cp$1@dont-email.me> Bytes: 3417 On 01/11/2024 12:50, druck wrote: > On 01/11/2024 10:24, The Natural Philosopher wrote: >> On 31/10/2024 21:54, druck wrote: >>> 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. >> >> I already told you the solution to that. >> >> There is a priority system in network manager. >> >> Otherwise it will connect to whatever it connected to last time, or >> sometimes not >> >> If you have more than one connection profile use: >> >> sudo nmcli c modify MYCONNECTIONNAME connection.autoconnect-priority 1 >> >> Randomly created connections are default priority zero >> >> This is also an accessible parameter from the GUI widget if you have a >> GUI interface >> >> It will then at least try only that SSID *first* >> >> Or delete any alternative connection profiles > > Except it doesn't actually work all the time. I've set up all my Pi's > which have both 2.4 GHz and 5 GHz WiFi with a higher priority to the > 5GHz network which has a different SSID to the 2.4 GHz one. Most of the > time they honour that but occasionally I find one has switched back to > 2.4 GHz, and it's not because the 5GHz signal strength has dropped > according to the logging. > Then delete the 2,4 GHZ SSID... > Network manager has not yet reached the required level of stability. > > ---druck -- Of what good are dead warriors? … Warriors are those who desire battle more than peace. Those who seek battle despite peace. Those who thump their spears on the ground and talk of honor. Those who leap high the battle dance and dream of glory … The good of dead warriors, Mother, is that they are dead. Sheri S Tepper: The Awakeners.