Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I know I will have to connect through wireless that is using WPA2/LEAP/AES.

Will my networkmanager connect to this network?

UPDATE: then why can't I find "AES" or CCMP in my nm-applet on Ubuntu 10.04?

share|improve this question
    
It surely supports WPA2-CCMP-AES. I'm pretty sure it does LEAP as well. – derobert Jan 21 '13 at 20:55
    
Yes it does.... – Ulrich Dangel Jan 21 '13 at 21:26

Wireless connections are handled through WPA Supplicant; which supports WPA2, LEAP, AES, and more.

share|improve this answer
    
NetworkManager does not handle all the type of connections that wpa_supplicant supports, so this is not sufficient. – BatchyX Jan 22 '13 at 8:43

According to the announcements for Fedora 13 (2010) NetworkManager suports WPA personal and enterprise.

share|improve this answer

NetworkManager can't support EAP security , the only way and (the best way) is using wpa_supplicant

To see what wireless networks are within range and to see what security they have enabled, use the command:

iwlist wlan0 scan

If iwlist returns an error saying it cannot scan because the interface is down, bring the interface up with ifconfig:

ifconfig wlan0 up

and then run the scan command again.

WPA Supplicant Configuration

Your /etc/wpa_supplicant.conf looks like this:

 # This line enables the use of wpa_cli which is used by rc.wireless
 # if possible (to check for successful association)
 ctrl_interface=/var/run/wpa_supplicant
 # By default, only root (group 0) may use wpa_cli
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1

network={ 
scan_ssid=1
mode=0
ssid="SSID_To_Connect_To"
proto=WPA
key_mgmt=WPA-EAP
pairwise=TKIP
group=TKIP
eap=LEAP
priority=2
auth_alg=LEAP
eapol_flags=0
identity="Your_User_Name"
password="Your_Password"
}

In the above configuration file, replace SSID_To_Connect_To with the Service Set IDentifier, or SSID, of the particular 802.11 wireless LAN you want to connect to; replace Your_User_Name with the user name used for authentication; and last, replace Your_Password with the password used for authentication.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.