NM starts wpa_supplicant -dd although wpa_supplicant is already started??
Hi, I am having a problem that NM starts wpa_supplicant on its own and ignores the fact that I have already started it. And than I have two wpa_supplicants running and the 1st one is being ignored. I start it wpa_supplicant with --w -B -ieth0 -Dwext -c/etc/wpa_supplicant and NM starts it with -dd -g /var/run/wpa_supplicant-global Can I somehow disable this? Or can I change start parameter for wpa_supplicant in NM? And how can I tell NM not to write its output in syslog? I can start it with --no-daemon /dev/ull 21 , but that's not a nice solution. Thanks a lot. M. -- Glauben heißt nicht wissen wollen, was wahr ist ... Nietzsche ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM starts wpa_supplicant -dd although wpa_supplicant is already started??
As I can see on the list , this is an old problem... I disabled my wpa_supplicant to avoid conflicts. But this makes NetworkManager unusefull. I am not able to connect to any of of my WPA2 APs at work. how should I enter these options: key_mgmt=IEEE8021X phase1=peaplabel=0 phase2=auth=MSCHAPV2 I tried with WPA2 Enterprise, but nothing happens ... It connected only once with success. It is just connecting forever ... and asks my for a password every 20 seconds ... and finally it connects to an another access point without encryption. and I didn't want that. And if I try not to use wpa_supplicant.conf any more and use only NetworkManager, how can I edit some saved connections? How can I change username or some other saved data? Any ideas ... I am really trying hard to use NetworkManager, but this is frustrating. Thanks. M. 2006/10/11, Ma Begaj [EMAIL PROTECTED]: Hi, I am having a problem that NM starts wpa_supplicant on its own and ignores the fact that I have already started it. And than I have two wpa_supplicants running and the 1st one is being ignored. I start it wpa_supplicant with --w -B -ieth0 -Dwext -c/etc/wpa_supplicant and NM starts it with -dd -g /var/run/wpa_supplicant-global Can I somehow disable this? Or can I change start parameter for wpa_supplicant in NM? And how can I tell NM not to write its output in syslog? I can start it with --no-daemon /dev/ull 21 , but that's not a nice solution. Thanks a lot. M. -- Glauben heißt nicht wissen wollen, was wahr ist ... Nietzsche -- Glauben heißt nicht wissen wollen, was wahr ist ... Nietzsche ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM starts wpa_supplicant -dd although wpa_supplicant is already started??
I /think/ that NM supports PEAP with mschapv2, can you post an output from the logs when you connect (editing out the confidential information). Here is information on running NM in debug mode: http://live.gnome.org/DarrenAlbers/NetworkManagerFAQ#head-5307e30269224aac6f7a4e83dc4c5b49386e7825 On 10/11/06, Ma Begaj [EMAIL PROTECTED] wrote: As I can see on the list , this is an old problem... I disabled my wpa_supplicant to avoid conflicts. But this makes NetworkManager unusefull. I am not able to connect to any of of my WPA2 APs at work. how should I enter these options: key_mgmt=IEEE8021X phase1=peaplabel=0 phase2=auth=MSCHAPV2 I tried with WPA2 Enterprise, but nothing happens ... It connected only once with success. It is just connecting forever ... and asks my for a password every 20 seconds ... and finally it connects to an another access point without encryption. and I didn't want that. And if I try not to use wpa_supplicant.conf any more and use only NetworkManager, how can I edit some saved connections? How can I change username or some other saved data? Any ideas ... I am really trying hard to use NetworkManager, but this is frustrating. Thanks. M. 2006/10/11, Ma Begaj [EMAIL PROTECTED]: Hi, I am having a problem that NM starts wpa_supplicant on its own and ignores the fact that I have already started it. And than I have two wpa_supplicants running and the 1st one is being ignored. I start it wpa_supplicant with --w -B -ieth0 -Dwext -c/etc/wpa_supplicant and NM starts it with -dd -g /var/run/wpa_supplicant-global Can I somehow disable this? Or can I change start parameter for wpa_supplicant in NM? And how can I tell NM not to write its output in syslog? I can start it with --no-daemon /dev/ull 21 , but that's not a nice solution. Thanks a lot. M. -- Glauben heißt nicht wissen wollen, was wahr ist ... Nietzsche -- Glauben heißt nicht wissen wollen, was wahr ist ... Nietzsche ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM starts wpa_supplicant -dd although wpa_supplicant is already started??
On Wed, 2006-10-11 at 09:15 -0400, Darren Albers wrote: I /think/ that NM supports PEAP with mschapv2, can you post an output from the logs when you connect (editing out the confidential information). Here is information on running NM in debug mode: http://live.gnome.org/DarrenAlbers/NetworkManagerFAQ#head-5307e30269224aac6f7a4e83dc4c5b49386e7825 The GUI bits for phase2 auth aren't there yet, and therefore the wpa_supplicant controller bits, so this won't work with NM yet. dan On 10/11/06, Ma Begaj [EMAIL PROTECTED] wrote: As I can see on the list , this is an old problem... I disabled my wpa_supplicant to avoid conflicts. But this makes NetworkManager unusefull. I am not able to connect to any of of my WPA2 APs at work. how should I enter these options: key_mgmt=IEEE8021X phase1=peaplabel=0 phase2=auth=MSCHAPV2 I tried with WPA2 Enterprise, but nothing happens ... It connected only once with success. It is just connecting forever ... and asks my for a password every 20 seconds ... and finally it connects to an another access point without encryption. and I didn't want that. And if I try not to use wpa_supplicant.conf any more and use only NetworkManager, how can I edit some saved connections? How can I change username or some other saved data? Any ideas ... I am really trying hard to use NetworkManager, but this is frustrating. Thanks. M. 2006/10/11, Ma Begaj [EMAIL PROTECTED]: Hi, I am having a problem that NM starts wpa_supplicant on its own and ignores the fact that I have already started it. And than I have two wpa_supplicants running and the 1st one is being ignored. I start it wpa_supplicant with --w -B -ieth0 -Dwext -c/etc/wpa_supplicant and NM starts it with -dd -g /var/run/wpa_supplicant-global Can I somehow disable this? Or can I change start parameter for wpa_supplicant in NM? And how can I tell NM not to write its output in syslog? I can start it with --no-daemon /dev/ull 21 , but that's not a nice solution. Thanks a lot. M. -- Glauben heißt nicht wissen wollen, was wahr ist ... Nietzsche -- Glauben heißt nicht wissen wollen, was wahr ist ... Nietzsche ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM starts wpa_supplicant -dd although wpa_supplicant is already started??
On Wed, 2006-10-11 at 16:33 +0200, Ma Begaj wrote: Hi and thanks for help. I am playing with NetworkManager all day long and google already found your page. There are 2 attachments in this email: 1. nm.log was created when I clicked on Connect to Other Wireless Network. I choosed WPA2 Enterprise, entered my identity and password and click to connect. 2. nm1.log was created when I just clicked on my access point without trying to configure anything. No succes in any of these tries. Hopefully, you can find something usefull. Your access point does not appear to be broadcasting its WPA or RSN Information Element, meaning that the access point is not using WPA. wpa_supplicant(8535): 0: 00:15:2b:34:51:c1 ssid='Datentankstelle802.1X' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 wpa_supplicant(8535):skip - no WPA/RSN IE Can you provide the output of 'iwlist eth0 scan' that describes the Datentankstelle802.1X access point? You should get something like this: Cell 04 - Address: 00:XX:XX:XX:XX:XX ESSID:foobar Protocol:IEEE 802.11bg Mode:Master Channel:1 Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s 6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Quality=82/100 Signal level=-48 dBm IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (2) : TKIP CCMP Authentication Suites (1) : PSK IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (2) : TKIP CCMP Authentication Suites (1) : PSK Preauthentication Supported Extra: Last beacon: 220ms ago If you don't see bits for IE:, the access point is not using WPA. Dan M. 2006/10/11, Darren Albers [EMAIL PROTECTED]: I /think/ that NM supports PEAP with mschapv2, can you post an output from the logs when you connect (editing out the confidential information). Here is information on running NM in debug mode: http://live.gnome.org/DarrenAlbers/NetworkManagerFAQ#head-5307e30269224aac6f7a4e83dc4c5b49386e7825 On 10/11/06, Ma Begaj [EMAIL PROTECTED] wrote: As I can see on the list , this is an old problem... I disabled my wpa_supplicant to avoid conflicts. But this makes NetworkManager unusefull. I am not able to connect to any of of my WPA2 APs at work. how should I enter these options: key_mgmt=IEEE8021X phase1=peaplabel=0 phase2=auth=MSCHAPV2 I tried with WPA2 Enterprise, but nothing happens ... It connected only once with success. It is just connecting forever ... and asks my for a password every 20 seconds ... and finally it connects to an another access point without encryption. and I didn't want that. And if I try not to use wpa_supplicant.conf any more and use only NetworkManager, how can I edit some saved connections? How can I change username or some other saved data? Any ideas ... I am really trying hard to use NetworkManager, but this is frustrating. Thanks. M. 2006/10/11, Ma Begaj [EMAIL PROTECTED]: Hi, I am having a problem that NM starts wpa_supplicant on its own and ignores the fact that I have already started it. And than I have two wpa_supplicants running and the 1st one is being ignored. I start it wpa_supplicant with --w -B -ieth0 -Dwext -c/etc/wpa_supplicant and NM starts it with -dd -g /var/run/wpa_supplicant-global Can I somehow disable this? Or can I change start parameter for wpa_supplicant in NM? And how can I tell NM not to write its output in syslog? I can start it with --no-daemon /dev/ull 21 , but that's not a nice solution. Thanks a lot. M. -- -- Glauben heißt nicht wissen wollen, was wahr ist ... Nietzsche ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Status of two phase auth
On Tue, Oct 10, 2006 at 11:56:59AM -0700, Joshua L. Phillips wrote: My University uses the same setup. Just click on the NM icon, select to connect to a new network, select WPA2 Enterprise, and just enter the SSID and your identity/password. It should take care of the rest. (Works for me anyways...) Sadly, this doesn't work for me. But judging from adjacent thread on this mailing list, only GUI bits are missing for 2-phase. So I will wait for GUI, then for release, and then I'll try persuading Ubuntu folks to put new NM in edgy-backports. Have a good day, -- Tomasz TorczOnly gods can safely risk perfection, [EMAIL PROTECTED] it's a dangerous thing for a man. -- Alia pgpJzVbtjfYKa.pgp Description: PGP signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems connecting to wireless network
Mitchell Mebane wrote: dragoran wrote: Hello, I have a laptop with a ipw3945 wireless interface card and using FC5 (x86_64) with wpa_supplicant-0.4.8-10.fc5 and NetworkManager-0.6.4-1.fc5. At work I have to configure this to be able to connect to the wireless network: 802.1x WEP dynamic EAP-PEAP with MS-CHAPv2 or EAP-TTLS with MS-CHAPv2 and login with my username and password But using networkmanager (I tryed wpa_enterprise and wpa2_enterprise) there is no option to select MS-CHAPv2 (wpa_supplicant man page says that it is supported). Is this config supported with networkmanager ? If not can I let networkmanager use a custom config file? If both does not work/ is not possible, is this support planned for 0.7 (or any later version) ? Please help my I have been searching in google in the last 2 weeks but found nothing, thats why I am asking here. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list I am also interested in getting EAP-PEAP with MSCHAPv2 working, as that's what my school network uses. Getting wireless working is really the only thing keeping me from switching to Linux at this point, so it would be nice if this is possible or planned. Thanks, Mitchell Mebane any ideas/comments? has anyone connected to a such a network using NM? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Status of NM with LEAP authentication feature.
Up to now I have been using NM with LEAP authentication on my FC5 machine. To do this I had to download the source from the CVS repository and compile. Will this version of NM be ever be ready as an RPM? In FC6 maybe? -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems connecting to wireless network
I have gotten this to work on FC5, but I have an Netgear MA401RA and a Microsoft MN-520 (both use the hostap drivers.) I had a few issues getting this going though. A few suggestions: 1. I would stop the NM service, start the wpa_supplicant service and use wpa_gui to try to negotiate a connection to the AP. If this works, then NM isn't configuring wpa_supplicant correctly. I don't know how to help this problem, but it might be a actual NM bug. However, if you still can't get a connection then you probably have a network configuration conflict. 2. I would make sure that you have no devices configured on your wireless card (system-config-network-gui) and that there are no aliases in your /etc/modprobe.conf file to you wireless card. 3. A lot of people startup wpa_supplicant at the END of their ifup-wireless script and stop using NM. However, I had to start wpa_supplicant at the BEGINNING of my ifup-wireless script (don't use any of the traditional configuration script, make it a big ELSE section if you are using wpa_supplicant.) The traditional setup was putting my driver into some kind of state that rendered wpa_supplicant ineffective once it was started. Maybe this will help a little... JLP dragoran wrote: Mitchell Mebane wrote: dragoran wrote: Hello, I have a laptop with a ipw3945 wireless interface card and using FC5 (x86_64) with wpa_supplicant-0.4.8-10.fc5 and NetworkManager-0.6.4-1.fc5. At work I have to configure this to be able to connect to the wireless network: 802.1x WEP dynamic EAP-PEAP with MS-CHAPv2 or EAP-TTLS with MS-CHAPv2 and login with my username and password But using networkmanager (I tryed wpa_enterprise and wpa2_enterprise) there is no option to select MS-CHAPv2 (wpa_supplicant man page says that it is supported). Is this config supported with networkmanager ? If not can I let networkmanager use a custom config file? If both does not work/ is not possible, is this support planned for 0.7 (or any later version) ? Please help my I have been searching in google in the last 2 weeks but found nothing, thats why I am asking here. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list I am also interested in getting EAP-PEAP with MSCHAPv2 working, as that's what my school network uses. Getting wireless working is really the only thing keeping me from switching to Linux at this point, so it would be nice if this is possible or planned. Thanks, Mitchell Mebane any ideas/comments? has anyone connected to a such a network using NM? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM on FC5
Gene Heskett wrote: Greetings; Apparently some update since back in mid-july has affected how the non-NM connections work as the profile I used for several weeks in the room next to this one no longer works, incapable of establishing a connection now. I even went through the system and deleted all copies of ifcfg-wlan0 except the one in /etc/sysconfig/network-scripts, but it still refuses to put the radio on the assigned channel of 6, but leaves it on channel 11 where there is no known access point. This is an FC5 install, 386 version on an HP dv5120us with a 64 bit turion cpu. The radio is a broadcomm 4318, and is driven by the ndiswrapper facility. iwlist outputs: [EMAIL PROTECTED] ~]# iwlist wlan0 scanning Warning: Driver for device wlan0 has been compiled with version 20 of Wireless Extension, while this program supports up to version 19. Some things may be broken... wlan0 Scan completed : Cell 01 - Address: 00:0F:66:77:73:A0 ESSID:xxx Protocol:IEEE 802.11g Mode:Managed Frequency:2.417 GHz (Channel 2) Quality:0/100 Signal level:-84 dBm Noise level:-256 dBm Encryption key:off Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s Extra:bcn_int=100 Extra:atim=0 Cell 02 - Address: 00:16:B6:CE:D1:9D ESSID:x Protocol:IEEE 802.11g Mode:Managed Frequency:2.437 GHz (Channel 6) Quality:0/100 Signal level:-69 dBm Noise level:-256 dBm Encryption key:off Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s Extra:bcn_int=100 Extra:atim=0 As can be seen, the signal on ch 6 is wall to wall, but I cannot connect. Can this possibly be related to the one char short ESSID thread I've been following here for quite some time? And if so, is it sufficient to just add a space to the end of the quoted string in my ifcfg-wlan0 file? Also, the setup instructions I have links to are for older versions of NM, this is whats installed right now, but all disabled. [EMAIL PROTECTED] ~]# rpm -qa|grep -i networkmanager NetworkManager-gnome-0.6.4-1.fc5 NetworkManager-vpnc-0.6.2-1.fc5 NetworkManager-0.6.4-1.fc5 NetworkManager-devel-0.6.4-1.fc5 NetworkManager-debuginfo-0.6.3-1.fc5 NetworkManager-glib-0.6.4-1.fc5 NetworkManager-glib-devel-0.6.4-1.fc5 Is there a fresh link describing howto setup these newer versions? And does it work well enough now its worth the extended hassle of trying to make it work? I am currently running on a dlink DWL-810+ radio plugged into the ethernet port. Which works just fine. -- Cheers, Gene ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM Connection Problem
I've had problems with APs that don't broadcast their SSIDs. Maybe this is the issue? Let me know if you figure it out. Thanks, JLP Jim Webb wrote: Joshua, I deleted the devices in system-network-config (eth0 eth1). There wasn't anything in modprobe.conf referring to eth1. I'm still having problems, but I'm thinking that it must be this AP, since I was able to connect to another network earlier today. Thanks, Jim - Original Message From: Joshua L. Phillips [EMAIL PROTECTED] To: networkmanager-list@gnome.org Sent: Wednesday, October 11, 2006 3:48:17 PM Subject: Re: NM Connection Problem Jim, I don't think this is a NM problem. Caveat: I could be wrong about that. On my box, my wireless card gets configured as wlan0, not eth1. While this isn't necessarily a problem, it could be that you have your wireless device configured using the standard wireless tools. Note: If your driver is automatically being registered as eth1 (without modprobe aliasing or being configured via wireless-tools), then this may not help at all: I would run system-config-network-gui (as root) and clean out any devices configured to use eth1 from your configuration. (If you aren't comfortable with that, then just create a new profile that only has the eth0 device selected and only use that profile with NM.) Also, edit /etc/modprobe.conf and comment-out any aliases for eth1 OR wlan0. Finally, reboot and see if this helps. (The reboot may be needed to cleanly reload your wireless driver.) This will ensure that the standard wireless tools do not try to configure your wireless device before NM gets a chance to configure it. Let me know if this helps (or if there are no configured eth1 devices or modprobe aliases to comment out)... JLP Jim Webb wrote: Joshua, Thanks for the reply. I have included the pertinent log info below...but I don't see anything wrong. Thanks again, Jim *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Oct 11 05:44:21 NetworkManager: information User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / stayonline Oct 11 05:44:21 NetworkManager: information Deactivating device eth1. Oct 11 05:44:21 dhclient: DHCPRELEASE on eth1 to 172.16.1.1 port 67 Oct 11 05:44:21 named[1516]: D-BUS: dhclient for interface eth1 released lease - removing forwarders. Oct 11 05:44:22 avahi-daemon[1986]: Interface eth1.IPv4 no longer relevant for mDNS. Oct 11 05:44:22 avahi-daemon[1986]: Leaving mDNS multicast group on interface eth1.IPv4 with address 172.16.1.138. Oct 11 05:44:22 avahi-daemon[1986]: Withdrawing address record for 172.16.1.138 on eth1. Oct 11 05:44:22 NetworkManager: information Device eth1 activation scheduled... Oct 11 05:44:22 NetworkManager: information Activation (eth1) started...Oct 11 05:44:22 NetworkManager: information Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Oct 11 05:44:22 NetworkManager: information Activation (eth1) Stage 1 of 5 (Device Prepare) started... Oct 11 05:44:22 NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... Oct 11 05:44:22 NetworkManager: information Activation (eth1) Stage 1 of 5 (Device Prepare) complete. Oct 11 05:44:22 NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) starting... Oct 11 05:44:22 NetworkManager: information Activation (eth1/wireless): access point 'stayonline' is unencrypted, no key needed. Oct 11 05:44:22 kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready Oct 11 05:44:22 NetworkManager: information SUP: sending command 'INTERFACE_ADD eth1wext/var/run/wpa_supplicant ' Oct 11 05:44:22 NetworkManager: information SUP: response was 'OK' Oct 11 05:44:22 NetworkManager: information SUP: sending command 'AP_SCAN 1' Oct 11 05:44:22 NetworkManager: information SUP: response was 'OK' Oct 11 05:44:22 NetworkManager: information SUP: sending command 'ADD_NETWORK' Oct 11 05:44:22 NetworkManager: information SUP: response was '0' Oct 11 05:44:22 NetworkManager: information SUP: sending command 'SET_NETWORK 0 ssid 737461796f6e6c696e65' Oct 11 05:44:22 NetworkManager: information SUP: response was 'OK' Oct 11 05:44:22 NetworkManager: information SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' Oct 11 05:44:22 NetworkManager: information SUP: response was 'OK' Oct 11 05:44:22 NetworkManager: information SUP: sending command 'ENABLE_NETWORK 0' Oct 11 05:44:22 NetworkManager: information SUP: response was 'OK' Oct 11 05:44:22 NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) complete. Oct 11 05:44:22 NetworkManager: information
Re: Problems connecting to wireless network
On 10/11/06, Darren Albers [EMAIL PROTECTED] wrote:
On 10/3/06, dragoran [EMAIL PROTECTED] wrote:
Hello,
I have a laptop with a ipw3945 wireless interface card and using FC5
(x86_64) with wpa_supplicant-0.4.8-10.fc5 and NetworkManager-0.6.4-1.fc5.
At work I have to configure this to be able to connect to the wireless
network:
802.1x
WEP dynamic
EAP-PEAP with MS-CHAPv2
or
EAP-TTLS with MS-CHAPv2
and login with my username and password
Actually let me change what I just said, I am not sure if Dan or
Robert ever intend to support dynamic WEP... Years ago I had a setup
very similar to that (PEAP with dynamic WEP) and I /think/ this was my
wpa_supplicant.conf. I had to do man wpa_supplicant and rely on my
memory to pull the relevant options:
network={
ssid=SSID
key_mgmt=IEEE8021X
eap=PEAP
auth_alg=OPEN
phase1=auth=MSCHAPV2
identity=username
password=password
}
While I understand that changing wireless setups is difficult in a
large enterprise (I work in IT Sec for a Global Enterprise with over
25k employees) leaving WEP in place, even dynamic WEP is not a good
idea and it would be a good time to upgrade.
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
