Dan,
are there any plans for Network Manager to handle hidden essid's?
i.e. using wpa_supplicant I can connect with the following config.

ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
network={
                ssid="MBI"
                scan_ssid=1
                eap=TLS
                key_mgmt=IEEE8021X
                pairwise=TKIP
                group=WEP104
                identity="[EMAIL PROTECTED]"
                ca_cert="/etc/eap/cacert.pem"
                client_cert="etc/eap/key.pem"
                private_key="/etc/eap/key.pem"
                private_key_passwd="whodareswins"
                eapol_flags=3
}

With networkmanager it never connects(the only way I have ever managed 
to connect was to quickly do a iwconfig eth0 essid MBI and then fingers 
crossed it worked once).

Jan 24 09:41:53 testmachine NetworkManager: <information>    User 
Switch: /org/freedesktop/NetworkManager/Devices/eth0 / MBI
Jan 24 09:41:53 testmachine NetworkManager: <information>    
Deactivating device eth0.
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0): cancelling...
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) cancellation handler scheduled...
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0): waiting for device to cancel activation.
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) cancellation handled.
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0): cancelled.
Jan 24 09:41:53 testmachine NetworkManager: <information>    Device eth0 
activation scheduled...
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) started...
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) Stage 1 of 5 (Device Prepare) started...
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) Stage 2 of 5 (Device Configure) scheduled...
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) Stage 1 of 5 (Device Prepare) complete.
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) Stage 2 of 5 (Device Configure) starting...
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0/wireless): access point 'MBI' is encrypted, but NO valid key 
exists.  New key needed.
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) New wireless user key requested for network 'MBI'.
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) Stage 2 of 5 (Device Configure) complete.
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) New wireless user key for network 'MBI' received.
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) Stage 1 of 5 (Device Prepare) started...
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) Stage 2 of 5 (Device Configure) scheduled...
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) Stage 1 of 5 (Device Prepare) complete.
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) Stage 2 of 5 (Device Configure) starting...
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0/wireless): access point 'MBI' is encrypted, and a key exists.  No 
new key needed.
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
sending command 'INTERFACE_ADD eth0        wext    
/var/run/wpa_supplicant    '
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
response was 'OK'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
sending command 'AP_SCAN 2'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
response was 'OK'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
sending command 'ADD_NETWORK'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
response was '0'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
sending command 'SET_NETWORK 0 ssid 49424d'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
response was 'OK'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
sending command 'SET_NETWORK 0 scan_ssid 1'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
response was 'OK'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
sending command 'SET_NETWORK 0 proto WPA'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
response was 'OK'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
sending command 'SET_NETWORK 0 key_mgmt WPA-EAP'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
response was 'OK'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
sending command 'SET_NETWORK 0 eap TLS'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
response was 'OK'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
sending command 'SET_NETWORK 0 identity "[EMAIL PROTECTED]"'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
response was 'OK'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
sending command 'SET_NETWORK 0 password <password>'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
response was 'OK'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
sending command 'SET_NETWORK 0 private_key "etc/eap/key.pem"'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
response was 'OK'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
sending command 'SET_NETWORK 0 private_key_passwd <key>'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
response was 'OK'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
sending command 'SET_NETWORK 0 client_cert "/etc/eap/key.pem"'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
response was 'OK'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
sending command 'SET_NETWORK 0 ca_cert "/etc/eap/cacert.pem"'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
response was 'OK'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
sending command 'ENABLE_NETWORK 0'
Jan 24 09:41:53 testmachine NetworkManager: <information>    SUP: 
response was 'OK'
Jan 24 09:41:53 testmachine NetworkManager: <information>    Activation 
(eth0) Stage 2 of 5 (Device Configure) complete.
Jan 24 09:42:33 testmachine NetworkManager: <information>    Activation 
(eth0/wireless): association took too long (>40s), failing activation.
Jan 24 09:42:33 testmachine NetworkManager: <information>    Activation 
(eth0) failure scheduled...
Jan 24 09:42:33 testmachine NetworkManager: <information>    Activation 
(eth0) failed for access point (MBI)
Jan 24 09:42:33 testmachine NetworkManager: <information>    Activation 
(eth0) failed.
Jan 24 09:42:33 testmachine NetworkManager: <information>    
Deactivating device eth0.
Jan 24 09:42:39 testmachine kernel: ADDRCONF(NETDEV_UP): eth0: link is 
not ready

_______________________________________________
NetworkManager-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Reply via email to