On Friday, 2 June 2023 07:16:41 BST Philip Webb wrote:
> 230601 Lee K wrote:
> > On Thu, Jun 01, 2023 at 11:09:50PM -0400, Philip Webb wrote:
> >> What is still not good is that that interface has "NO-CARRIER".
> >> Also, 'rc-status' after a reboot shows wpa_supplicant as STOPPED.
> >>
> >> 'rc-service -v wpa_supplicant start' gets it STARTED,
> >> but 'ip a' still shows "NO-CARRIER".
> >> I tried 'ip link set wlp5s0 carrier on',
> >> but was told "operation not supported".
> >>
> >> w_s seems to be finding its conf file
> >> at /etc/wpa_supplicant/wpa_supplicant.conf ,
> >> but 'wpa_cli' continues to say "can't link to wpa_supplicant".
> >>
> >> I have checked the service name + password are correct in the conf file.
> >
> > Can you post the contents of wpa_supplicant.conf..?
>
> #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, or whatever is the version of your installed wpa_supplicant package. 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) 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. Either way, look at 'man wpa_passphrase' if you ever want to generate a key. > I have put wpa_supplicant in the default services started at boot. Good. > There was also a suggestion to create a symlink net.wlp5s0 > pointing to net.lo both in /etc/init.d ; it's not there now. This would be needed for more granular network configuration - it depends on your particular use case requirements (different NICs, APs, gateways, static IPs, etc.). If you have added wpa_supplicant in your default level rc scripts then you don't need both.
signature.asc
Description: This is a digitally signed message part.
