GNOME.org
 

Re: NM starts wpa_supplicant -dd although wpa_supplicant is already started??

On Thu, 2006-10-12 at 11:35 +0200, Ma Begaj wrote:
> Hi,
> 
> I don't see any IE bits, but this is the configuration which I use to
> connect and it is correct:

If you don't see any IE bits, then of course wpa_supplicant can't
connect to the access point!  There may one or both of two issues:

1) Your ipw2200 drivers are too old to put the WPA IE into the scan
results.  Could you show the output of dmesg for 'ipw2200' and
'ieee80211' ?  It should be something like this:

ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.2kmprq
ipw2200: Copyright(c) 2003-2006 Intel Corporation
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)

ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno linux intel com>

2) The access point is not broadcasting the Information Element.  The AP
_MUST_ be broadcasting the Information Element, otherwise it's not a WPA
access point and you cannot use WPA with it, no matter what OS you're
using.  It _may_ be the case that you have multiple access points, using
the same SSID, that use different options, and the scan you performed
did not pick up all the access points in your SSID.  Try doing a couple
scans in various locations to see whether you can pick up other access
points with the same SSID, and a WPA or RSN IE.

Dan

> network={
>   ssid="Datentankstelle802.1X
>   scan_ssid=1
>   proto=WPA
>   key_mgmt=IEEE802.1X
>   eap=TTLS
>   phase1="peaplabel=0"
>   phase2="auth=MSCHAPV2"
>   identity="username"
>   password="password"
> }
> 
> br and thanks
> 
> M.
> 
> 
> 
> 2006/10/11, Dan Williams <dcbw redhat com>:
> > 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 <dalbers gmail com>:
> > > > 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 <derliebegott gmail com> 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 <derliebegott gmail com>:
> > > > > > 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 2>&1 &", but that's not a nice
> > > > > > solution.
> > > > > >
> > > > > > Thanks a lot.
> > > > > >
> > > > > > M.
> > > > > >
> > > > > > --
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Glauben hei� 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
> >
> >
> 
>
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]