On Wednesday 25 December 2024 02:01:43 GMT Philip Webb wrote: > 241224 Michael wrote:
> > Did he *only* change the SSID and password > > or did he also change the encryption and key management method ? > > Only the former : he's not skilled enough to do the latter. > I suspect that originally someone set it up for him > & altered some default setting(s), then when he restarted it, > the default setting(s) returned & that's not working with my software. In this case you may only have to edit the SSID entry in your wpa_supplicant.conf and leave the rest as is. Since you can connect using the wpa_gui with the same password, let's start by paying attention to the SSID. > > Check there are no empty spaces left at the end of the strings > > in any entries you edited in your wpa_supplicant.conf. > > There are none. I think you'll find there is at least one within the SSID - see below. > > Check you have not altered the access rights of the file : > > chmod -v 600 /etc/wpa_supplicant/wpa_supplicant.conf > > The permission is '644', which is ok for my cellpbone's hotspot. This is a security issue for your WiFi password details being exposed in your filesystem and to stop non-root users altering your settings. It is recommended only root has access to this file, but in any case it is not affecting the problem you are experiencing. > >> I can use 'wpa_gui' with a bit of fussing & editing. > > > > Currently, it shows the correct adapter + service name & below it lists : > >> Status : completed (station) > >> Last message : <blank> > >> Authentication : WPA2-PSK > >> Encryption : CCMP + TKIP > >> SSID : <service name> > >> BSSID : < 12 hex digits > > >> IP address : < 11 digits > > > > > The first method looks good to me, beyond the points I mentioned above. > > > > Check what the landlord's AP wants to use by running wpa_cli in a > > terminal: > > > scan > > > > will start scanning for APs. after few secs, you will have some results : > > > scan_results > > It shows nothing : see output below. It does provide some useful info, although you do not show the scan_results output provided by wpa_cli. > Thanks for your usually very helpful suggestions (smile). > Here is the output via 'wpa_cli' as I start & stop Wifi. > I connect & disconnect with my cell-phone 'Athene' + landlord's service, > whose name is 'Watch Iovedocs ... ', > & which I have to access via 'wpa_gui' (I used 2 terminals). [snip ...] > using wpa_gui to start/stop landlord's 'Watch ... ' : > > <3>WNM: Preferred List Available > <3>SME: Trying to authenticate with 68:ff:7b:47:c9:13 (SSID='watch > iovedocs on YouTube ' freq=5200 MHz) <3>CTRL-EVENT-REGDOM-CHANGE init=CORE > type=WORLD > <3>Trying to associate with 68:ff:7b:47:c9:13 > (SSID='watch iovedocs on YouTube ' freq=5200 MHz) Please check the space character shown at the end of the SSID string above. You will need to include this in your wpa_supplicant.conf; e.g.: ssid="watch iovedocs on YouTube " > -- end of output -- > > I've had difficulty determining the exact sequence of commands with wpa_gui. > It seems to be : 'manage networks' -- 'edit' to add password -- 'save' -- > 'scan' : a list of services is offered, a '5200' is double-clicked -- back > to 'current status' -- 'connect' & it fills in the details > & takes another 15 sec to get an IP address & I/net cb accessed. > > Any further suggestions very welcome. After I launch the wpa_gui I press scan, double click the preferred AP, add credentials and if necessary change the authentication method, and 'save'. It should pick it up thereafter, but if already associated with another AP, I may have to select from the "Network" drop down my preferred AP. I expect when you edit the SSID as suggested above you will be able to connect without using the GUI.
signature.asc
Description: This is a digitally signed message part.
