230602 Michael wrote:
> On Friday, 2 June 2023 07:16:41 BST Philip Webb wrote:
>> #wpa_supplicant.conf 230601
>>
>> network={
>> ssid="<Wifi service provider>"
>> bssid=AA:BB:CC:DD:EE:FF
>> proto=RSN
>> key_mgmt=WPA-PSK
>> pairwise=CCMP
>> auth_alg=OPEN
>> group=CCMP
>> psk="<Wifi password>"
>> ieee80211w=2
>> priority=5
>> }
>
> Have a look at your
> /usr/share/doc/wpa_supplicant-2.10-r1/wpa_supplicant.conf.bz2
Thanx : I tend to look at 'man' & forget the dox in /usr/share .
I've copied it all into this regular machine & will look thro' it ;
there's an awful lot of info, but some tiny note mb the solution (grin).
> If you define ieee80211w=2 for obligatory 'management frame protection',
> I understand you'll need :
> key_mgmt=WPA-PSK WPA-PSK-SHA256 (for WPA2)
> or
> key_mgmt=SAE (Simultaneous Authentication of Equals for WPA3 only)
I tried both, but no change.
> Meanwhile, PSK stands for "Pre-Shared Key".
> This is meant to be either 64 hex-digits (32 bytes)
> or an ASCII passphrase which will be used to generate the PSK with the SSID,
> when the configuration file is processed by wpa_supplicant .
> Typically a passphrase is used with domestic WiFi routers.
This Wifi belongs to my landlord & is just over my head in the house.
IIRC it runs on Ubuntu (he uses Mac for his home-office).
He's amiable, but no tech specialist (he distributes movies for a living).
> Either way, look at 'man wpa_passphrase' if you ever want to generate a key.
The password looks like 'M343477M' (all different characters).
It works with SR + Mint.
Today's investigations :
(1) I copied the BT- firmware ( 2 files) from SR
into /lib/firmware/mediatek on the new machine : no change.
'dmesg | grsp firmware' gives
Spectre V2 : Enabling Restricted Speculation for firmware calls.
Loading firmware : regulatory.db
Loading firmware : regulatory.db.p7s
mediatek /WIFI_MT7961_patch_mcu_1_2_hdr.bin
mediatek /WIFI_RAM_CODE_MT7961_1.bin [repeated once]
At the end of dmesg it says :
mt7921e : renamed from wlan0
(2) w_s dox : one suggested conf file has simply :
network {
ssid="simple"
psk="<password>"
priority=5
}
This makes no difference.
(3) You didn't comment on the failure of w-s to start in default runlevel.
The final lines before login are :
INIT : Entering runlevel : 3
Waiting for uevents to be processed ...
[RED] Could not find a wireless interface
[RED] ERROR : wpa_supplicant failed to start
starting DHCP client Daemon
Mounting network filesystems
Starting local
The first red msg is from the w-s script in /etc/init.d .
I wonder whether w-s sb trying to start before the DHCP deamon ?
It has no difficulty starting via 'rc-service' after login.
Unfortunately, I can't explore how SF + Mint handle this,
as they both use Systemd, not Openrc, which I am using.
I'll look thro' the /usr/share dox as carefully as I can.
Your comment on my final query wb very welcome
or any other thoughts you might have.
--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca
