Re: WPA troubles in F12
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@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Internet connection sharing
When doing that, in the IPv4 tab, choose the Shared IPv4 method. Then, hook up your wired cable, and pick your new shared connection from the menu. NM will now NAT the wired subnet to the current default connection, which I assume would be your wifi. You can also share 3G - wired this way. Or 3G - wifi. etc. That. Is freaking awesome. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WPA troubles in F12
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@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
WPA troubles in F12
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@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NetworkManager 0.7.1 failing with university's WPA2-Enterprise wifi
Hello there. I've been trying for about a week and a half to get my Fedora 11 laptop working with my university's wifi network. It is a WPA2-enterprise, certificate-using, PEAP, MSCHAPV2 type of wireless network. I am certain I know my wireless access user name and password, and even the domain (although I'm not sure if that's useful). I have the certificate and the connection working fine under Windows. I cannot get it to work under Fedora. I wish I could give more useful information -- my WPA wifi won't work isn't good enough for a bug report, I haven't proven anything's wrong. But I'm no fool and relatively linux-savvy. Is there any reason why a WPA+certificate network might not be able to work under Linux? The funny thing is, I actually got it to work last Friday, without question, all day. When I changed my password over the weekend though, I couldn't log on to it on Monday or hereafter. (My nm-version from Fedora-stable is 0.7.1-git-20090708, so the software hasn't been changed.) If it helps, I've heard that some of my Mac friends are having trouble getting on to it, but that might be a red herring. In the past (back at college) I'd just ignore this and go back to Windows. But I really want it to work -- there's no reason why it shouldn't. Are there any pointers or anything I could have missed? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
