I have a network I need to connect to which uses WPA2 with AES and PEAP with MSCHAP v2 and unable to authenticate.
Does Gnome network manager supports the configuration of WPA2 with AES and MSCHAP v2 of PEAP?
On 08/29/2012 04:56 AM, ajpeck wrote:
>
> I have a network I need to connect to which uses WPA2 with AES and PEAP
> with MSCHAP v2 and unable to authenticate.
>
> Does Gnome network manager supports the configuration of WPA2 with AES
> and MSCHAP v2 of PEAP?
Yes, NM supports WPA2-AES, but your device driver might not. We cannot tell as
you failed to tell us what device you are using. At least you did mention that
you are using 12.1.
The MSCHAP v2/PEAP means that you are using either a VPN, or WPA2 Enterprise.
Which is it?
Others with the exact same model laptop as me with MS Windows 7 (even Win XP works) are able to authenticate and connect to network.
The laptop is Acer TravelMate 5740G with Acer Nplify 802.11b/g/n wireless device.
It is WPA2 Enterprise.
this might be useful
03:00.0 Network controller: Atheros Communications Inc. AR9287 Wireless Network Adapter (PCI-Express) (rev 01)
Subsystem: Foxconn International, Inc. Device e034
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at b2000000 (64-bit, non-prefetchable) [size=64]
Capabilities: <access denied>
Kernel driver in use: ath9k[/size]
On 08/30/2012 01:16 AM, ajpeck wrote:
>
> this might be useful
>
> 03:00.0 Network controller: Atheros Communications Inc. AR9287 Wireless
> Network Adapter (PCI-Express) (rev 01)
> Subsystem: Foxconn International, Inc. Device e034
> Flags: bus master, fast devsel, latency 0, IRQ 17
> Memory at b2000000 (64-bit, non-prefetchable) [size=64]
> Capabilities: <access denied>
> Kernel driver in use: ath9k
No, that is irrelevant. Does your device see the AP with ‘sudo /usr/sbin/iwlist
scan’? If so, your device is working.
Once you get the configuration correct, your device will work. I used MSCHAP2
authentication with Linux over 10 years ago. It was not for wireless then, but
it works. You will need to set up the connection with the NM applet’s “Manage
Connections” method. I don’t use either Gnome or WPA2 Enterprise, thus I cannot
provide more details on how you do it.
[/size]
I do see ‘ap’ when I run with ‘sudo /usr/sbin/iwlist scan’. I also see the network I want to connect to.
When I used the application Gnome Network Connections to setup the configuration for the network I don’t have a field to select TKIP or AES, I presume it is choosing TKIP by default.
On the Wireless tab, I have:
- Mode set to ‘Infrastructure’
On the Wireless Security tab, I have:
- Security set to ‘WPA & WPA2 Enterprise’
- Authentication set to ‘Protected EAP (PEAP)’
- CA certificate set to ‘(None)’ {not used for wireless access}
- PEAP version set to ‘Automatic’
- Inner authentication set to ‘MSCHAPv2’
On 08/31/2012 12:06 AM, ajpeck wrote:
>
> I do see ‘ap’ when I run with ‘sudo /usr/sbin/iwlist scan’. I also see
> the network I want to connect to.
>
> When I used the application Gnome Network Connections to setup the
> configuration for the network I don’t have a field to select TKIP or
> AES, I presume it is choosing TKIP by default.
On the KDE applet, it says “WPA/WPA2 Enterprise”. NM will use TKIP if WPA and
AES if WPA2. That is automatic.
>
> On the Wireless tab, I have:
> - Mode set to ‘Infrastructure’
>
> On the Wireless Security tab, I have:
> - Security set to ‘WPA & WPA2 Enterprise’
> - Authentication set to ‘Protected EAP (PEAP)’
> - CA certificate set to ‘(None)’ {not used for wireless access}
> - PEAP version set to ‘Automatic’
> - Inner authentication set to ‘MSCHAPv2’
Assuming that you have set the MSCHAPv2 username and password correctly, that
should work. As I do not use Gnome, and I do not have access to an enterprise
server, that is about as far as I can go. Are you sure that no certificate is used?
You should look at /var/lof/NetworkManager for any other clues.
>
>