linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Thomas Backlund <tmb@mandriva.org>
Cc: Tomas Winkler <tomasw@gmail.com>, 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 12:04:59 -0400	[thread overview]
Message-ID: <1212768299.14803.2.camel@localhost.localdomain> (raw)
In-Reply-To: <48495E85.9050608@mandriva.org>

On Fri, 2008-06-06 at 18:57 +0300, Thomas Backlund wrote:
> Dan Williams skrev:
> > On Fri, 2008-06-06 at 18:12 +0300, Tomas Winkler wrote:
> >> On Fri, Jun 6, 2008 at 5:51 PM, Thomas Backlund <tmb@mandriva.org>=
 wrote:
> >>> Tomas Winkler skrev:
> >>>> On Fri, Jun 6, 2008 at 3:33 PM, Thomas Backlund <tmb@mandriva.or=
g> wrote:
> >>>>> Thomas Backlund skrev:
> >>>>>> Tomas Winkler skrev:
> >>>>>>> On Fri, Jun 6, 2008 at 3:44 AM, Ian Schram <ischram@telenet.b=
e> 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 mac=
80211?
> >>>>>>>>
> >>>>>>>> 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=
=2E
> >>>>
> >>>> :iwlcore:iwl_send_static_wepkey_cmd+0xcb/0xd5
> >>>> :iwlcore:iwl_set_default_wep_key+0xa2/0xbc
> >>>>
> >>>> Try to set the encryption explicitly
> >>>> network=3D{
> >>>>    psk=3D"*************************"
> >>>>    scan_ssid=3D1
> >>>>    ssid=3D"dlink"
> >>>>    pairwise=3DCCMP
> >>>>   group=3DCCMP
> >>>>  }
> >>>>
> >>>>
> >>> That didn't help at all...
> >>>
> >>> What's more it prevented the wifi to work on 2.6.24.7 so I had to=
 remove the
> >>> lines again...
> >>>
> >> So what's your AP configuration TKIP?
> >=20
> > Yeah, the supplicant log he posted clearly shows that the GTK is TK=
IP.
> >=20
> > =EF=BB=BF> 1212763152.516781: wpa_driver_wext_set_key: alg=3D2 key_=
idx=3D1 set_tx=3D0 seq_len=3D6 key_len=3D32
> >> 1212763152.516790: WPA: Key negotiation completed with 00:xx:xx:xx=
:xx:xx [PTK=3DCCMP GTK=3DTKIP]
> >=20
>=20
> The AP is actually set for TKIP+AES
>=20
> BTW, is that better or worse than a clean AES ?
> I'm reading up on it, but I get a lot of conflicting info...

It's less secure than straight AES.

WEP < TKIP < AES/CCMP

Dan

> > Dan
> >=20
> >> Second try also with sw decryption:
> >>
> >> in /etc/modprobe.conf
> >> options iwl4965 swcrypto=3D1
> >>
> >>
> >> Tomas
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe linux-wi=
reless" in
> >> the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >=20
>=20
> Thomas

--
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:[~2008-06-06 16:05 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
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 [this message]
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=1212768299.14803.2.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).