Unsupported Authenication Modes
I have NM working nicely for our home networks, thanks to all involved.
Now, I am trying to set up a laptop running ubuntu for easy use by my
daughter who is at Edinburgh (UK) University. (She is reading
Comparative Religion and not Computer Science!) Unfortunately I am not
anywhere near Edinburgh so I want to get as close to the solution as
possible, by diligent research, before I get to see the network. Anyway
I hate trialerror methods - they take far too much time! She will
require, therefore, four different networks: home wireless, uni wired
(not allowed to use wireless in halls), uni wireless, wireless
hotspots. EUCS website suggests that a wpa-supplicant file for their
network should look something like this:
QUOTE
ap_scan=2
network={
ssid=central-wpa
auth_alg=OPEN
key_mgmt=WPA_EAP
proto=WPA
pairwise=TKIP
group=TKIP
eap=PEAP
identity=username
password=password
phase1=peapver=0
phase2=auth=MSCHAPV2
eapol_flags=3
UNQUOTE
Apart from the typo (I think it should be WPA-EAP not WPA_EAP), this
looks as if it requires two-phase
authentication which, from reading all the stuff I can find here and in
ubuntu etc, looks as if it may not be supported by NM.
1. Am I correct in concluding that this mode of wpa-supplicant is not
supported by NM?
2. Am I correct in concluding that manual configuration of
wpa-supplicant.conf is ignored by NM?
3. If so, is it possible to use NM in conjunction with an ifup/down
script fired from a suitable applet?
4. Would it be a good idea/possible to have an option in NM to use a
custom script for this type of situation?
Very grateful for any comments and/or ideas ...
Charles Whittington
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Suggestion: Static WPA Networks
It seems that some users on the mailing list along with myself are having a similar problem:that is we need to connect to a particular WPA network that wpa_supplicant supports but network-manager does not.so, what if you could create some sort of /etc/nm- wpa.conf file that read like a wpa_supplicantconfiguration file, and network manager would add a menu option in the popup menu to connectto any networks you have explicitly defined in that file. This would make a nice temporary solution until the GUI configuration adds support for those protocols.As it is now, I have to disable NM, then pop open two command lines, one for wpa_supplicant,and another to run dhclient once wpa displays Authenticated The connection drops fairly frequently as well, with no indication except that my network apps stop working, then i haveto go back to my two terminals and do the same process over again, complete with retypingmy password for sudo. The entire process is a bit of a pain. If network-manager could handle networks that I manually define and configure, and reconnect automatically when they drop,it would make my life much easier.This would also make any improvements to wpa_supplicant effectively included and supported by NetworkManager instantly, even if it takes a while to update the interface.Thanks for making a great product,Zach Tibbitts - [EMAIL PROTECTED] http://collegegeek.org ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Suggestion: Static WPA Networks
Hello. On Fri, 2006-11-03 at 10:24, Zach Tibbitts wrote: so, what if you could create some sort of /etc/nm-wpa.conf file that read like a wpa_supplicant configuration file, and network manager would add a menu option in the popup menu to connect to any networks you have explicitly defined in that file. This would make a nice temporary solution until the GUI configuration adds support for those protocols. But it also means to do work twice. I don't think one of the current devs will work on such a temporary solution, but will work on a better integration of the opions in nm. Sorry, we know all the different opions from wpa_supplicant needs still a lot of work. Support for config files, wpa_supplicant or even openvpn, is something Dan and Robert are not happy with. I'm not sure if they accept a patch for it, but you can try it anyway. regards Stefan Schmidt signature.asc Description: Digital signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Unsupported Authenication Modes
Hello. On Fri, 2006-11-03 at 12:45, Charles Whittington wrote: phase1=peapver=0 phase2=auth=MSCHAPV2 eapol_flags=3 These config options are not yet supported in nm. I'm working on a subset of it. See my mails about EAP/TTLS for more details. Apart from the typo (I think it should be WPA-EAP not WPA_EAP), this looks as if it requires two-phase authentication which, from reading all the stuff I can find here and in ubuntu etc, looks as if it may not be supported by NM. 1. Am I correct in concluding that this mode of wpa-supplicant is not supported by NM? Right. The framework is already there, but we don't have the GUI bits to ask for the information and transfer them to wpa_supplicant. 2. Am I correct in concluding that manual configuration of wpa-supplicant.conf is ignored by NM? Right. 3. If so, is it possible to use NM in conjunction with an ifup/down script fired from a suitable applet? What do you mean here? Same as in question 4? 4. Would it be a good idea/possible to have an option in NM to use a custom script for this type of situation? You mean starting a script to use another wpa_supplicant with config fired up from the ifup/ifdown scripts integrated in NetworkManagerDispatcher? I never tried this. Not sure what happen if two version of wpa_supplicant are running. The one form nm and the one from your custom script. regards Stefan Schmidt signature.asc Description: Digital signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
some question about wireless connection
hi,there please help me to know what different between link quality and signal level, which one is measure of the signal better or not. I found some wireless device which used ndiswrapper only supply signal level, not link quality.Could I use the signal level to measure the signal good or not? Another, how can I link to Ad-hoc by Networkmanager? Thank you very much!-- --Pang Dawei ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Unsupported Authenication Modes
3. If so, is it possible to use NM in conjunction with an ifup/down script fired from a suitable applet? What do you mean here? Same as in question 4? 4. Would it be a good idea/possible to have an option in NM to use a custom script for this type of situation? You mean starting a script to use another wpa_supplicant with config fired up from the ifup/ifdown scripts integrated in NetworkManagerDispatcher? I never tried this. Not sure what happen if two version of wpa_supplicant are running. The one form nm and the one from your custom script. regards Stefan Schmidt Thanks very much for your prompt reply. You have answered Question 3 to Question 4. Q4 was meant to be rather like the post following mine from Zach Tibbitts - i.e. could we have a temporary workaround for this situation a) to allow our users to use NM for all connections, and b) so that you guys are not always having to play catch-up with what is happening in wpa-supplicant? Is it worth me saying to the user: when connecting to uni network (i.e. one requiring unsupported modes), select no Network in NM and then run this script? Or will that still start two wpa_supplicants? Charles Whittington // ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Unsupported Authenication Modes
Hello. On Fri, 2006-11-03 at 17:58, Charles Whittington wrote: Is it worth me saying to the user: when connecting to uni network (i.e. one requiring unsupported modes), select no Network in NM and then run this script? Or will that still start two wpa_supplicants? Why not just write a small script which stops nm and start wpa_supplicant with commandline options and config file. Write another script which kills wpa_supplicant and starts nm. Call it uni-network-start and uni-network-stop, put it on the desktop and give it two fancy icons. :) You can extend such shell wrappers to your needs. My point is, that all the workarounds should be outside the code of nm. If we touch nm code we should do it right. regards Stefan Schmidt signature.asc Description: Digital signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Unsupported Authenication Modes
Hello. On Fri, 2006-11-03 at 14:05, Zach Tibbitts wrote: I don't suppose NM has some sort of plugin-interface for some third party to write up a quick hack, does it? It has an interface for vpn-plugins. For other stuff you can use dbus. Please see an earlier thread on this ml about it. regards Stefan Schmidt signature.asc Description: Digital signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
