From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] strange problem with Wifi
Date: Fri, 27 Dec 2024 09:52:00 +0000 [thread overview]
Message-ID: <2971946.e9J7NaK4W3@rogueboard> (raw)
In-Reply-To: <Z23_B8hG8CGVaiNt@ca.inter.net>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
On Friday 27 December 2024 01:12:39 GMT Philip Webb wrote:
> 241225 Michael wrote:
> > I expect when you edit the SSID as suggested above
> > you will be able to connect without using the GUI.
>
> Indeed ! -- that was the problem.
> I've added the space & commented the 3 extra lines re keys/security
> & there's no problem connecting via 'rc-service -v wpa_supplicant start'
> I keep copies of the config files for both services
> & overwrite 'wpa_supplicant.conf' when necessary
> (of course, I use a Bash aliases).
>
> Thanks for all the advice : what a strange problem.
I've learned the hard way it's easy to press the space bar inadvertently and
not notice a space character at the end of a string. In this case it would be
noticeable when you run 'scan_results' with wpa_cli, because the SSID is
enclosed in single quotes.
Alternatively, you can use the BSSID to connect to an AP. The BSSID won't
change when the AP owner alters the SSID. This may be less desirable if you
are connecting to a mesh network with multiple APs, or you move around in a
building with more than one AP.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-12-27 9:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 23:35 [gentoo-user] strange problem with Wifi Philip Webb
2024-12-24 10:53 ` Michael
2024-12-25 2:01 ` Philip Webb
2024-12-25 2:18 ` William Kenworthy
2024-12-25 10:42 ` Michael
2024-12-27 1:12 ` Philip Webb
2024-12-27 9:52 ` Michael [this message]
2024-12-25 13:38 ` Alexis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2971946.e9J7NaK4W3@rogueboard \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox