WPA troubles in F12

[Jud Craft]

Hello again.

After a fresh (and now updated) install of Fedora 12 Beta, I'm having
a huge problem getting my university's wifi connection to work with
networkmanager.  I've been trying for hours and I can't make it
happen.

It's one of those WPA2/enterprise/certificate type connections, and
I've tried nearly every possible connection of login data,
certificate, and encryption, and just can't get it work.

F11 was rough at first, but I eventually got it to work.  F12 is
giving me a headache.  Is there nothing I could do to help find out
what's wrong here?  I've seen the NetworkManager "authentication"
dialog so many times I'm starting to mistrust the UI.
_______________________________________________
NetworkManager-list mailing list
NetworkManager-list@...
http://mail.gnome.org/mailman/listinfo/networkmanager-list

[Jud Craft]

Is there a networkmanager troubleshooting list?  I hate to add noise,
but I'm tired of wandering through Google for random openssl commands
and other rain-dances.  I've been doing that with WPA-certificate wifi
ever since I gave Linux a try again three years ago.

I took the F12 upgrade to finally rid myself of Windows.  I don't just
want -- I *need* -- to figure out why NM isn't working for me, or even
if it is NM in the first place.  But I have no clue where to start.

I see wpa_supplicant service enabled in F12.  Is there something wrong
with my university's wifi network and certificate?  (How would I
figure that out?  Why would all my non-Linux friends on Mac and
Windows connect just fine?)
_______________________________________________
NetworkManager-list mailing list
NetworkManager-list@...
http://mail.gnome.org/mailman/listinfo/networkmanager-list

[Rui Tiago Cação Matos]

2009/11/6 Jud Craft <craftjml@...>:

> Is there a networkmanager troubleshooting list?  I hate to add noise,
> but I'm tired of wandering through Google for random openssl commands
> and other rain-dances.  I've been doing that with WPA-certificate wifi
> ever since I gave Linux a try again three years ago.
>
> I took the F12 upgrade to finally rid myself of Windows.  I don't just
> want -- I *need* -- to figure out why NM isn't working for me, or even
> if it is NM in the first place.  But I have no clue where to start.
>
> I see wpa_supplicant service enabled in F12.  Is there something wrong
> with my university's wifi network and certificate?  (How would I
> figure that out?  Why would all my non-Linux friends on Mac and
> Windows connect just fine?)

Most of the times it's just Linux drivers sucking. Anyway, you should
provide this list (or better, file a bug[1]) with some logs from the
kernel and NM.

You can also try to debug how wpa_supplicant and your driver are
working and send those logs too. See, for instance, Dan's explanation
of how to do that at:

http://mail.gnome.org/archives/networkmanager-list/2008-March/msg00096.html

Rui

[1] https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager
_______________________________________________
NetworkManager-list mailing list
NetworkManager-list@...
http://mail.gnome.org/mailman/listinfo/networkmanager-list

[Jud Craft]

> You can also try to debug how wpa_supplicant and your driver are
> working and send those logs too. See, for instance, Dan's explanation
> of how to do that at:

I will.  This is the open-source intel 4965 driver, and it worked fine
in F11, so I can't see any reason why it should cease to work fine
now.  (Unlike xorg-intel, I don't think wireless drivers have had
major rewrites lately).

If I run into anything I'll be back.
_______________________________________________
NetworkManager-list mailing list
NetworkManager-list@...
http://mail.gnome.org/mailman/listinfo/networkmanager-list

[Jud Craft]

I'm back.  I've run into something.

First, I stopped NetworkManager service, and then tried creating a
simple wpa_supplicant configuration file, like so...

-----
ap_scan=1
fast_reauth=1

network={
        ssid="networkname"
        scan_ssid=1
        key_mgmt=WPA-EAP
        eap=PEAP
        identity="username"
        password="mypassword"
        phase1="peaplabel=PEAPTYPE"
        phase2="auth=MSCHAPV2"
}
-----

Excecuted with:  /usr/sbin/wpa_supplicant -ddd -i wlan0 -c
wpacert-soms.conf -D wext

As you can see I left out the certificate line.  This did work
successfully, if PEAPTYPE=0.  (Type 1 did not work).  I don't have any
logs, but I'd be happy to post them if anyone would like to see.

I then did the following steps in NetworkManager:

1.  Selected "networkname" under the network menu.
2.  Entered the same data from the conf file (MSCHAP, PEAP=0, no certificate).

I then connected!  Voila!  This connection worked, although I had to
click "Ignore" on the Don't Use Certificate question box.

3.  Then, I opened up the connection ("Edit Connections"), and set the
certificate for it in NetworkManager.
4.  To top it off, I tried setting PEAP to Automatic.

And then it connected again!  Amazing.

5.  I then restarted the computer, and logged back in.
6.  NetworkManager failed to connection after several times.

Wait.  What happened here?  It was just working.

7.  I deleted the NetworkManager connection, and then re-selected the
network in the menu.
8.  I added the original settings (PEAP=0, no certificate) again.

I connected again!

9.  I opened the connection and set the certificate and PEAP to Automatic.

And then it connected!  Until I restarted my computer again...


So this is my dilemma.  Certificate+PEAP=Automatic doesn't seem to
work on its own.  However, if I try to connect to the network with
PEAP=0, no certificate, then the connection is successful, AND
subsequent connections (as Iong as I don't restart the computer) are
successful with the certificate and PEAP=Automatic.

This has happened consistently.  Why does NM connect correctly with
the certificate+PEAP=Auto, only after I've previously connected with
NoCertificate+PEAP=0?  If anyone has any debugging advice I'd be happy
to follow it.
_______________________________________________
NetworkManager-list mailing list
NetworkManager-list@...
http://mail.gnome.org/mailman/listinfo/networkmanager-list

[Dan Williams]

On Sat, 2009-11-07 at 21:39 -0500, Jud Craft wrote:

> I'm back.  I've run into something.
>
> First, I stopped NetworkManager service, and then tried creating a
> simple wpa_supplicant configuration file, like so...
>
> -----
> ap_scan=1
> fast_reauth=1
>
> network={
> ssid="networkname"
> scan_ssid=1
> key_mgmt=WPA-EAP
> eap=PEAP
> identity="username"
> password="mypassword"
> phase1="peaplabel=PEAPTYPE"
> phase2="auth=MSCHAPV2"
> }
> -----
>
> Excecuted with:  /usr/sbin/wpa_supplicant -ddd -i wlan0 -c
> wpacert-soms.conf -D wext
>
> As you can see I left out the certificate line.  This did work
> successfully, if PEAPTYPE=0.  (Type 1 did not work).  I don't have any
> logs, but I'd be happy to post them if anyone would like to see.
>
> I then did the following steps in NetworkManager:
>
> 1.  Selected "networkname" under the network menu.
> 2.  Entered the same data from the conf file (MSCHAP, PEAP=0, no certificate).
>
> I then connected!  Voila!  This connection worked, although I had to
> click "Ignore" on the Don't Use Certificate question box.
>
> 3.  Then, I opened up the connection ("Edit Connections"), and set the
> certificate for it in NetworkManager.
> 4.  To top it off, I tried setting PEAP to Automatic.
>
> And then it connected again!  Amazing.
>
> 5.  I then restarted the computer, and logged back in.
> 6.  NetworkManager failed to connection after several times.
>
> Wait.  What happened here?  It was just working.
>
> 7.  I deleted the NetworkManager connection, and then re-selected the
> network in the menu.
> 8.  I added the original settings (PEAP=0, no certificate) again.
>
> I connected again!
>
> 9.  I opened the connection and set the certificate and PEAP to Automatic.
>
> And then it connected!  Until I restarted my computer again...
>
>
> So this is my dilemma.  Certificate+PEAP=Automatic doesn't seem to
> work on its own.  However, if I try to connect to the network with
> PEAP=0, no certificate, then the connection is successful, AND
> subsequent connections (as Iong as I don't restart the computer) are
> successful with the certificate and PEAP=Automatic.
>
> This has happened consistently.  Why does NM connect correctly with
> the certificate+PEAP=Auto, only after I've previously connected with
> NoCertificate+PEAP=0?  If anyone has any debugging advice I'd be happy
> to follow it.

Can you grab /var/log/messages from a successful run (cert+peap0) and a
failed run so I can look at what NM is sending to the supplicant?

Also, can you do the manual supplicant runs with "-dddt" and get a
successful run so that I can debug what's going on with the supplicant?
We can follow up after that.

Basically, we want a clean successful supplicant run, then we want to
reboot and grab a debug log from NM controlling the supplicant and
compare the two.  But lets do that after looking at /var/log/messages
and the manual supplicant runs.

Dan

_______________________________________________
NetworkManager-list mailing list
NetworkManager-list@...
http://mail.gnome.org/mailman/listinfo/networkmanager-list

[Jud Craft]

I have not forgotten about this and will gather the needed data.  Just
happen to be life-busy for the current time.

On Tue, Nov 17, 2009 at 5:15 PM, Dan Williams wrote:>
> Can you grab /var/log/messages from a successful run (cert+peap0) and a
> failed run so I can look at what NM is sending to the supplicant?

Please note that my initial successful run is only with NoCert+Peap0.
Once I connect in this manner, subsequent Cert+Peap0(or Automatic)
connections work just fine (for the duration of the session).
_______________________________________________
NetworkManager-list mailing list
NetworkManager-list@...
http://mail.gnome.org/mailman/listinfo/networkmanager-list