linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Thomas Backlund <tmb@mandriva.org>,
	Ian Schram <ischram@telenet.be>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwl4965 oops in 2.6.26-rc5 x86_64
Date: Fri, 06 Jun 2008 10:29:29 -0400	[thread overview]
Message-ID: <1212762569.28631.6.camel@localhost.localdomain> (raw)
In-Reply-To: <1ba2fa240806060659wf4e4088s8afdd2f7f854ea09@mail.gmail.com>

On Fri, 2008-06-06 at 16:59 +0300, Tomas Winkler wrote:
> On Fri, Jun 6, 2008 at 3:33 PM, Thomas Backlund <tmb@mandriva.org> wrote:
> > Thomas Backlund skrev:
> >>
> >> Tomas Winkler skrev:
> >>>
> >>> On Fri, Jun 6, 2008 at 3:44 AM, Ian Schram <ischram@telenet.be> wrote:
> >>>>
> >>>> Isn't this the Oops Joonwoo Park wanted to patch with
> >>>>
> >>>> "[PATCH] iwlwifi: fix oops on wep key insertion" 27/5/2008
> >>>>
> >>>> invalid length of webkey that would/should be handled in mac80211?
> >>>>
> >>>> ian
> >>>
> >>> Yes, it looks like.
> >>
> >> Ummm, what has a wep key to do with me trying to access a WPA2-Personal
> >> encrypted net ?
> 
> Not sure yet, but mac is trying to assign default/static wep key.

The output of wpa_supplicant with "-dddt" would be quite useful in
figuring this out.

The supplicant does always _clear_ static WEP keys when it starts the
interface, when a connection drops, and when it quits.  Maybe that's
where it's coming from?  But it should just be setting the "disabled"
bit in the WEXT structure and sending a key of all zeros.

Dan

> :iwlcore:iwl_send_static_wepkey_cmd+0xcb/0xd5
> :iwlcore:iwl_set_default_wep_key+0xa2/0xbc
> 
> Try to set the encryption explicitly
> network={
>     psk="*************************"
>     scan_ssid=1
>     ssid="dlink"
>     pairwise=CCMP
>    group=CCMP
>  }
> 
> 
> >>
> >>> Thomas can you send out your wpa_supplicant config fiele
> >>>
> >>
> >> I could, but since I would have to remove any sensitive info such as the
> >> psk key, would it be of any use ?
> >
> > Anyway, here configs are:
> >
> > wpa_supplicant.conf
> > (I stripped all the comments from the file)
> > --- cut ---
> > ctrl_interface=/var/run/wpa_supplicant
> >
> > eapol_version=1
> >
> > ap_scan=1
> >
> > fast_reauth=1
> >
> > blob-base64-exampleblob={
> > SGVsbG8gV29ybGQhCg==
> > }
> >
> > network={
> >    psk="*************************"
> >    scan_ssid=1
> >    ssid="dlink"
> > }
> > --- cut ---
> >
> > ifcfg-wlan0
> > --- cut ---
> > DEVICE=wlan0
> > BOOTPROTO=dhcp
> > ONBOOT=yes
> > METRIC=35
> > MII_NOT_SUPPORTED=no
> > USERCTL=no
> > RESOLV_MODS=no
> > WIRELESS_MODE=Managed
> > WIRELESS_ESSID=dlink
> > WIRELESS_ENC_KEY='s:*************************'
> > WIRELESS_WPA_DRIVER=wext
> > IPV6INIT=no
> > IPV6TO4INIT=no
> > DHCP_CLIENT=dhclient
> > NEEDHOSTNAME=no
> > PEERDNS=yes
> > PEERYP=yes
> > PEERNTPD=no
> > --- cut ---
> >
> >>
> >>> I will provide a patch that disable hw encryption on long wep keys. It
> >>> get lost in my todo list.
> >>> Tomas
> >>>
> >>
> >
> > --
> > Thomas
> >
> >
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" 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:[~2008-06-06 14:29 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05 17:55 iwl4965 oops in 2.6.25-rc5 x86_64 Thomas Backlund
2008-06-05 18:03 ` Tomas Winkler
2008-06-05 18:09   ` Thomas Backlund
2008-06-05 20:10     ` Thomas Backlund
2008-06-05 21:48       ` iwl4965 oops in 2.6.26-rc5 x86_64 Thomas Backlund
2008-06-06  0:44         ` Ian Schram
2008-06-06 11:32           ` Tomas Winkler
2008-06-06 12:01             ` Thomas Backlund
2008-06-06 12:33               ` Thomas Backlund
2008-06-06 13:59                 ` Tomas Winkler
2008-06-06 14:29                   ` Dan Williams [this message]
2008-06-06 14:48                     ` Thomas Backlund
2008-06-06 14:51                   ` Thomas Backlund
2008-06-06 15:12                     ` Tomas Winkler
2008-06-06 15:22                       ` Dan Williams
2008-06-06 15:57                         ` Thomas Backlund
2008-06-06 16:04                           ` Dan Williams
2008-06-06 21:43                       ` Thomas Backlund
2008-06-06 23:59                         ` Tomas Winkler
2008-06-07 13:28                           ` Thomas Backlund
2008-06-08 10:27                             ` Tomas Winkler
2008-06-08 12:21                               ` Thomas Backlund
2008-06-08 15:31                                 ` Tomas Winkler
2008-06-08 20:07                                   ` Thomas Backlund
2008-06-09 15:55                                   ` Dan Williams
2008-06-09 16:43                                     ` Tomas Winkler
2008-06-09 16:54                                       ` Dan Williams
2008-06-10 14:48         ` QUESTIONS to ieee80211_beacon_get AND ieee80211_get_buffered_bc Joe
2008-06-10 14:58           ` Johannes Berg
2008-06-10 14:58           ` Johannes Berg
     [not found]             ` <484E9B84.1070902@gmx.de>
2008-06-10 15:46               ` [english 87%] " Johannes Berg
2008-06-10 15:34           ` [english 95%] " Joe
2008-06-10 15:40             ` Johannes Berg

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=1212762569.28631.6.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=ischram@telenet.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tmb@mandriva.org \
    --cc=tomasw@gmail.com \
    /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).