From: Sedat Dilek <sedat.dilek@googlemail.com>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: mac80211: Breakage in software encryption (iwl3945)
Date: Sun, 24 Jan 2010 11:40:37 +0100 [thread overview]
Message-ID: <2d0a357f1001240240k6e8eaefdm3633d3c6e5e30597@mail.gmail.com> (raw)
In-Reply-To: <1264277460.13250.10.camel@maxim-laptop>
Hi,
it is very helpful to give commit-id *and* commit-msg so that others
can follow more easily.
Which GIT repository (branch) is that?
Kind Regards,
- Sedat -
On Sat, Jan 23, 2010 at 9:10 PM, Maxim Levitsky <maximlevitsky@gmail.com> wrote:
> I updated the kernel and lost connection to my WPA2
> AP. Strangely the WPA handshake completes, but DHCP not.
>
> I also unfortunately found that all that time I was using software
> encryption (this is iwl3945 loaded with swcrypto=1).
> Hardware encryption doesn't work ether and didn't work in the slightly
> older kernel (but it did work once, I sure)
>
> Now, the commit a6bae9e7ab19876a157c91019852395539e4f20e breaks software
> encryption, with behaviour like described above.
>
> Best regards,
> Maxim Levitsky
>
> --
> 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
>
next prev parent reply other threads:[~2010-01-24 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 20:10 mac80211: Breakage in software encryption (iwl3945) Maxim Levitsky
2010-01-24 10:32 ` Marcus Better
2010-01-24 11:15 ` Marcus Better
2010-01-24 10:40 ` Sedat Dilek [this message]
2010-01-24 10:56 ` Johannes Berg
2010-01-24 18:24 ` Maxim Levitsky
2010-01-24 23:27 ` Jochen Friedrich
2010-01-25 0:05 ` Jochen Friedrich
2010-01-25 9:32 ` Johannes Berg
2010-01-25 15:10 ` Maxim Levitsky
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=2d0a357f1001240240k6e8eaefdm3633d3c6e5e30597@mail.gmail.com \
--to=sedat.dilek@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=sedat.dilek@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