241225 Michael wrote: M> Check there are no empty spaces left at the end of the strings > in any entries you edited in your wpa_supplicant.conf. P> There are none. M> I think you'll find there is at least one within the SSID - see below. P> 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) M> 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 " > 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. -- ========================,,============================================ SUPPORT ___________//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT `-O----------O---' purslowatcadotinterdotnet
