linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ветошкин Никита" <nvetoshkin@naumen.ru>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: mac80211 and SIOCSIWAUTH
Date: Fri, 09 Nov 2007 01:13:32 +0500	[thread overview]
Message-ID: <47336DEC.2040007@naumen.ru> (raw)
In-Reply-To: <1194552053.31657.0.camel@localhost.localdomain>

Is anybody interested in this case?
If so, what information should I provide you which be enough to=20
investigate the problem?
- kernel 2.6.23-gentoo
- iwl3945 1.1.21
- ucode 2.14.1
- wpa_supplicant 0.6.0

What else(logs,output)?

Vetoshkin Nikita


Dan Williams =D0=BF=D0=B8=D1=88=D0=B5=D1=82:
> On Thu, 2007-11-08 at 23:46 +0500, =D0=92=D0=B5=D1=82=D0=BE=D1=88=D0=BA=
=D0=B8=D0=BD =D0=9D=D0=B8=D0=BA=D0=B8=D1=82=D0=B0 wrote:
>> Hi, I'm a user of Lenovo R61 laptop with Intel 3945 wireless card. I=
=20
>> have Gentoo and would like to use the iwlwifi + wpa_supplicant drive=
r,=20
>> but I can't because Wi-Fi installed in our office needs WPA2=20
>> authentication and I can't connect to it. There no problems using ip=
w3945d.
>> #wpa_supplicant config
>> ap_scan=3D2
>> network=3D{
>>          ssid=3D"point1"
>>          key_mgmt=3DWPA-EAP
>>          scan_ssid=3D1
>>          identity=3D"nvetoshkin"
>>          proto=3DWPA2
>>          eap=3DTLS
>>          ca_cert=3D"/home/nekto/certificate.pem"
>>          private_key=3D"/home/nekto/nvetoshkin.p12"
>>          private_key_passwd=3D"nvetoshkin"
>> }
>> ioctl[SIOCSIWAUTH]: Operation not supported - this error always appe=
ars=20
>> in wpa_supplicant output. I digged a bit in source code and found ou=
t=20
>> that it is mac80211 subsystem who returns ENOTSUP.
>> Is it really the cause of my problems or am I just confused?
>=20
> There's a number of SIOCSIWAUTH sub-options, and not all are necessar=
y,
> and not all are supported by every driver.  That's normal.  Ignore th=
e
> wpa_supplicant message.
>=20
> Dan
>=20
>=20
> -
> To unsubscribe from this list: send the line "unsubscribe linux-wirel=
ess" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>=20

--=20
=D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC,
=D0=92=D0=B5=D1=82=D0=BE=D1=88=D0=BA=D0=B8=D0=BD =D0=9D=D0=B8=D0=BA=D0=B8=
=D1=82=D0=B0

=D0=98=D0=BD=D0=B6=D0=B5=D0=BD=D0=B5=D1=80 =D0=BF=D0=BE=D0=B4=D0=B4=D0=B5=
=D1=80=D0=B6=D0=BA=D0=B8 =D1=81=D0=B8=D1=81=D1=82=D0=B5=D0=BC IP-=D1=82=
=D0=B5=D0=BB=D0=B5=D1=84=D0=BE=D0=BD=D0=B8=D0=B8
=D0=A1=D0=B5=D1=80=D0=B2=D0=B8=D1=81=D0=BD=D1=8B=D0=B9 =D1=86=D0=B5=D0=BD=
=D1=82=D1=80
=D0=9A=D0=BE=D0=BC=D0=BF=D0=B0=D0=BD=D0=B8=D1=8F Naumen
-
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2007-11-08 20:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 18:46 mac80211 and SIOCSIWAUTH Ветошкин Никита
2007-11-08 20:00 ` Dan Williams
2007-11-08 20:13   ` Ветошкин Никита [this message]
2007-11-09  1:23 ` Zhu Yi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47336DEC.2040007@naumen.ru \
    --to=nvetoshkin@naumen.ru \
    --cc=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).