Find the answer to your Linux question:
Results 1 to 4 of 4
I have a system that I'm trying to connect to a wireless network protected with WPA2-PEAP and every time I get a "Bad Password" error from wicd and NetworkManager (neither ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Mar 2011
    Posts
    68

    Connecting to WPA2-PEAP


    I have a system that I'm trying to connect to a wireless network protected with WPA2-PEAP and every time I get a "Bad Password" error from wicd and NetworkManager (neither where installed at the same time!)

    I'm sure it isn't a problem with the driver, I can connect to WPA2-home, WEP, and Open networks just fine. And it isn't the wireless network per say, several other devices connect without issue, each running Android, iOS, Windows NT, and OS X

    I have revisited the possibility of me mistyping my username and password several times, this is not the issue, nor is a corrupt LDAP user object.

    As the Arch Linux wiki suggested, I tried using GTC instead of standard WPA2-PEAP, this did not work either.

    Right now the only thing I can think of is that because the network is using a self-signed certificate, my laptop is dropping the connection as soon as it is established which would account for the "local choice, reason 3" in my dmesg output.

    Also, you will notice in my lsmod output that the Intel wireless driver "is not loaded" this is because I have statically compiled it into my kernel binary.

    lspci -knn output:
    Code:
    00:00.0 Host bridge [0600]: Intel Corporation Ivy Bridge DRAM Controller 
    [8086:0154] (rev 09)
            Subsystem: Lenovo Device [17aa:3977]
            Kernel driver in use: agpgart-intel
    00:02.0 VGA compatible controller [0300]: Intel Corporation Ivy Bridge 
    Graphics Controller [8086:0166] (rev 09)
            Subsystem: Lenovo Device [17aa:3977]
            Kernel driver in use: i915
    00:14.0 USB controller [0c03]: Intel Corporation Panther Point USB xHCI Host 
    Controller [8086:1e31] (rev 04)
            Subsystem: Lenovo Device [17aa:3977]
            Kernel driver in use: xhci_hcd
    00:16.0 Communication controller [0780]: Intel Corporation Panther Point MEI 
    Controller #1 [8086:1e3a] (rev 04)
            Subsystem: Lenovo Device [17aa:3977]
    00:1a.0 USB controller [0c03]: Intel Corporation Panther Point USB Enhanced 
    Host Controller #2 [8086:1e2d] (rev 04)
            Subsystem: Lenovo Device [17aa:3977]
            Kernel driver in use: ehci_hcd
    00:1b.0 Audio device [0403]: Intel Corporation Panther Point High Definition 
    Audio Controller [8086:1e20] (rev 04)
            Subsystem: Lenovo Device [17aa:3977]
            Kernel driver in use: snd_hda_intel
    00:1c.0 PCI bridge [0604]: Intel Corporation Panther Point PCI Express Root 
    Port 1 [8086:1e10] (rev c4)
            Kernel driver in use: pcieport
    00:1c.1 PCI bridge [0604]: Intel Corporation Panther Point PCI Express Root 
    Port 2 [8086:1e12] (rev c4)
            Kernel driver in use: pcieport
    00:1c.2 PCI bridge [0604]: Intel Corporation Panther Point PCI Express Root 
    Port 3 [8086:1e14] (rev c4)
            Kernel driver in use: pcieport
    00:1d.0 USB controller [0c03]: Intel Corporation Panther Point USB Enhanced 
    Host Controller #1 [8086:1e26] (rev 04)
            Subsystem: Lenovo Device [17aa:3977]
            Kernel driver in use: ehci_hcd                                                                                                                                      
    00:1f.0 ISA bridge [0601]: Intel Corporation Panther Point LPC Controller 
    [8086:1e57] (rev 04)                                                                              
            Subsystem: Lenovo Device [17aa:3977]                                                                                                                                
    00:1f.2 SATA controller [0106]: Intel Corporation Panther Point 6 port SATA 
    Controller [AHCI mode] [8086:1e03] (rev 04)                                                     
            Subsystem: Lenovo Device [17aa:3977]                                                                                                                                
            Kernel driver in use: ahci                                                                                                                                          
    00:1f.3 SMBus [0c05]: Intel Corporation Panther Point SMBus Controller 
    [8086:1e22] (rev 04)                                                                                 
            Subsystem: Lenovo Device [17aa:3977]                                                                                                                                
    02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
    RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 05)                             
            Subsystem: Lenovo Device [17aa:3975]                                                                                                                                
            Kernel driver in use: r8169
    03:00.0 Network controller [0280]: Intel Corporation Centrino Wireless-N 2200 
    [8086:0891] (rev c4)
            Subsystem: Intel Corporation Centrino Wireless-N 2200 BGN [8086:4222]
            Kernel driver in use: iwlwifi
    lsmod output:
    Code:
    vboxnetflt             15021  0 
    vboxdrv              1780220  1 vboxnetflt
    kvm_intel             119803  0 
    kvm                   340511  1 kvm_intel
    crc32c_intel            1888  0 
    aesni_intel            41486  2 
    cryptd                  7477  1 aesni_intel
    aes_x86_64              7356  1 aesni_intel
    dmesg | grep firmware output:
    Code:
    [    2.060257] iwlwifi 0000:03:00.0: loaded firmware version 18.168.6.1
    dmesg | grep wlan0 output:
    Code:
    [  527.500970] wlan0: deauthenticating from 00:21:1c:79:c1:a7 by local choice 
    (reason=3)
    [  528.318248] wlan0: authenticate with 00:21:1c:79:c1:a7
    [  528.321466] wlan0: send auth to 00:21:1c:79:c1:a7 (try 1/3)
    [  528.323533] wlan0: authenticated
    [  528.323978] wlan0: associate with 00:21:1c:79:c1:a7 (try 1/3)
    [  528.327961] wlan0: RX AssocResp from 00:21:1c:79:c1:a7 (capab=0x431 
    status=0 aid=1)
    [  528.331971] wlan0: associated
    [  530.343486] wlan0: deauthenticating from 00:21:1c:79:c1:a7 by local choice 
    (reason=3)
    [  530.812804] wlan0: authenticate with 00:21:1c:79:c1:a7
    [  530.816341] wlan0: send auth to 00:21:1c:79:c1:a7 (try 1/3)
    [  530.818051] wlan0: authenticated
    [  530.819038] wlan0: associate with 00:21:1c:79:c1:a7 (try 1/3)
    [  530.822215] wlan0: RX AssocResp from 00:21:1c:79:c1:a7 (capab=0x431 
    status=0 aid=1)
    [  530.826848] wlan0: associated
    [  532.840837] wlan0: deauthenticating from 00:21:1c:79:c1:a7 by local choice 
    (reason=3)
    uname -r output:
    Code:
    3.5.0-gentoo
    Last edited by bleedingsamurai; 08-17-2012 at 11:16 PM. Reason: additional information

  2. #2
    Linux Newbie hagfish52's Avatar
    Join Date
    Dec 2011
    Location
    Asheville, NC
    Posts
    225
    I googled this, and a few people reported they found instances of wpa_supplicant running; when they killed wpa_supplicant the problem went away.

  3. #3
    Just Joined!
    Join Date
    Mar 2011
    Posts
    68
    Interesting, I'll have to double check that the next time I try to connect to this network.

    Correct me if I'm wrong, but isn't wpa_supplicant needed for the kind of wireless connection I'm trying to make?

  4. $spacer_open
    $spacer_close
  5. #4
    Linux Newbie hagfish52's Avatar
    Join Date
    Dec 2011
    Location
    Asheville, NC
    Posts
    225
    Not necessarily. I don't know what you are using for wireless management, but wpa_supplicant is an alternative to Network Manager or Xsupplicant, so if two of the programs are running at the same time they can interfere with one another.

    [EDIT]

    I see you are using Network Manager. Network Manager uses wpa_supplicant. In this case you want to check for multiple instances of the wpa_supplicant daemon.

    You may also want to consider using Xsupplicant instead of Network Manager; it supports many EAP types.
    Last edited by hagfish52; 08-18-2012 at 05:08 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •