Bug 243134 - Can't connect to WLAN since F8 builds
Can't connect to WLAN since F8 builds
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Christopher Aillon
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-06-07 10:07 EDT by Bastien Nocera
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-06-07 15:27:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bastien Nocera 2007-06-07 10:07:37 EDT
NetworkManager-0.6.5-3.fc8
wpa_supplicant-0.5.7-3.fc7

Looks like NetworkManager can't connect to wpa_supplicant anymore.

Jun  7 15:00:58 snoogens NetworkManager: <info>  SWITCH: no current connection,
found better connection 'wlan0'.
Jun  7 15:00:58 snoogens dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
Jun  7 15:00:58 snoogens NetworkManager: <info>  Will activate connection
'wlan0/idoru'.
Jun  7 15:00:58 snoogens NetworkManager: <info>  Device wlan0 activation
scheduled...
Jun  7 15:00:58 snoogens NetworkManager: <info>  Activation (wlan0) started...
Jun  7 15:00:58 snoogens NetworkManager: <info>  Activation (wlan0) Stage 1 of 5
(Device Prepare) scheduled...
Jun  7 15:00:58 snoogens NetworkManager: <info>  Activation (wlan0) Stage 1 of 5
(Device Prepare) started...
Jun  7 15:00:58 snoogens NetworkManager: <info>  Activation (wlan0) Stage 2 of 5
(Device Configure) scheduled...
Jun  7 15:00:58 snoogens NetworkManager: <info>  Activation (wlan0) Stage 1 of 5
(Device Prepare) complete.
Jun  7 15:00:58 snoogens NetworkManager: <info>  Activation (wlan0) Stage 2 of 5
(Device Configure) starting...
Jun  7 15:00:58 snoogens NetworkManager: <info>  Activation (wlan0/wireless):
access point 'idoru' is encrypted, but NO valid key exists.  New key needed.
Jun  7 15:00:58 snoogens NetworkManager: <info>  Activation (wlan0) New wireless
user key requested for network 'idoru'.
Jun  7 15:00:58 snoogens NetworkManager: <info>  Activation (wlan0) Stage 2 of 5
(Device Configure) complete.
Jun  7 15:00:58 snoogens NetworkManager: <info>  Activation (wlan0) New wireless
user key for network 'idoru' received.
Jun  7 15:00:58 snoogens NetworkManager: <info>  Activation (wlan0) Stage 1 of 5
(Device Prepare) scheduled...
Jun  7 15:00:58 snoogens NetworkManager: <info>  Activation (wlan0) Stage 1 of 5
(Device Prepare) started...
Jun  7 15:00:58 snoogens NetworkManager: <info>  Activation (wlan0) Stage 2 of 5
(Device Configure) scheduled...
Jun  7 15:00:58 snoogens NetworkManager: <info>  Activation (wlan0) Stage 1 of 5
(Device Prepare) complete.
Jun  7 15:00:58 snoogens NetworkManager: <info>  Activation (wlan0) Stage 2 of 5
(Device Configure) starting...
Jun  7 15:00:58 snoogens NetworkManager: <info>  Activation (wlan0/wireless):
access point 'idoru' is encrypted, and a key exists.  No new key needed.
Jun  7 15:01:00 snoogens NetworkManager: <info>  Error opening supplicant global
control interface. 
Jun  7 15:01:00 snoogens NetworkManager: <WARN>  real_act_stage2_config():
Activation (wlan0/wireless): couldn't connect to the supplicant.
Jun  7 15:01:00 snoogens NetworkManager: <info>  Activation (wlan0) failure
scheduled... 
Jun  7 15:01:00 snoogens NetworkManager: <info>  Activation (wlan0) Stage 2 of 5
(Device Configure) complete.
Jun  7 15:01:00 snoogens NetworkManager: <info>  Activation (wlan0) failed for
access point (idoru) 
Jun  7 15:01:00 snoogens NetworkManager: <info>  Activation (wlan0) failed. 
Jun  7 15:01:00 snoogens NetworkManager: <info>  Deactivating device wlan0.

Setting up the connection by hand with ifcfg network scripts works just fine.
Comment 1 Christopher Aillon 2007-06-07 15:27:58 EDT
You need NM 0.6.5-4.  We removed a CLI option to the supplicant and removed the
call from NM so you needed to ugprade both.
Comment 2 Christopher Aillon 2007-06-07 15:39:20 EDT
Ah oops, forgot to build that in rawhide.  Get -3.fc7 (not -3.fc8) or -5.fc8
tomorrow.

Note You need to log in before you can comment on or make changes to this bug.