Bug 444856

Could you enable supplicant logging?  Add "-dddt" to the OTHER_FLAGS line in
/etc/sysconfig/wpa_supplicant, restart, and then attach
/var/log/wpa_supplicant.log to this bug report after having attempted a
connection to your AP.  Thanks!

Add "-dddt" to OTHER_ARGS I mean, not OTHER_FLAGS.

Hello,

Here's the requested info: /var/log/wpa_supplicant.log only lists:

[root@mazarin ~]# cat /var/log/wpa_supplicant.log
Could not request DBus service name: already registered.
Could not request DBus service name: already registered.
Could not request DBus service name: already registered.
1209642029.889509: Providing DBus service 'fi.epitest.hostap.WPASupplicant'.
1209642029.898318: Daemonize..

However, here's what I get in a background terminal, by manually invoking
wlassistant:

[root@mazarin ~]# wlassistant
Loaded application options.
All interfaces: eth0, sit0, virbr0, wlan0, wmaster0
Wireless interface(s): wlan0
Permissions checked.
DHCP Client: dhclient
All executables found.
scan: /sbin/iwlist wlan0 scan
Networks found: 1
No DHCP client running.
No pre-connection command specified.
iwconfig_set: /sbin/iwconfig wlan0 mode managed channel 9 key off essid zando
iwconfig_ap: /sbin/iwconfig wlan0 ap 00:19:5B:0E:A6:27
==>stderr: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or
directory
Using wpa_supplicant driver: wext
WPA client started. Waiting for status...
==>stderr: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or
directory
CONNECTION FAILED.
disconnect: /sbin/iwconfig wlan0 mode managed key off ap off essid off


...and remains at the above line until I manually close wlassistant. "zando" is
the SSID of my wireless network.


Regards,
Răzvan

Hello,

Now the wpa_supplicant not starting at boot seems to be fixed (it starts OK
now), but I still can't connect to the wireless network (at least with wlassistant).

Could you please indicate a *canonical* (= Red Hat manual-like ;-) ) way to
start, stop the wireless connection, change the IP address, verify the
connection & signal strength, etc.  ?

Should I use the "classic" system-config-network or NetworkManager ? 

wlassistant-0.5.7-7.fc9.x86_64
wpa_supplicant-0.6.3-5.fc9.x86_64
NetworkManager-0.7.0-0.9.3.svn3623.fc9.i386
NetworkManager-0.7.0-0.9.3.svn3623.fc9.x86_64

Regards,
Răzvan

NetworkManager is the canonical way to do this in F9.  Can you try with NM?

Thanks for your info !


Now that wpa_supplicant starts automatically at boot, I will enable NM to start
at boot also (if not already).

Could you please detail the *next steps* I should follow to configure and test
the wireless interface using NM ? For example:

- assign a manual IP (*or* an automatic one by DHCP - but I don't have DHCP in
all networks)
- insert my WPA2 preshared key (password) and complete authentication;
- monitor the wireless network (signal strength, other parameters, etc.), best
via a graphical GNOME applet.


Thanks a lot,
Răzvan

Hello,

After the last updates (I'm running Fedora 9 preview release with latest updates
as of May 13, 2008) *and* after enabling NetworkManager, wireless connection
"magically" started to work.

However, when enabling the wireless interface (that uses WPA2), two dialogs show up:

- one asking for the WPA2 preshared key;
- one stating:

"Enter password for default keyring to unlock.

The application NetworkManager Applet /usr/bin/nm-applet wants access to default
keyring, but it is locked".

Since I didn't setup any key on my keyring, I have no password to insert.
Clicking Deny leads however to succesful connection, but the dialog is strange
for non-technical users.

Regards,
Răzvan

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping