From: Michael Buesch <mb@bu3sch.de>
To: Daniel Drake <dsd@gentoo.org>
Cc: netdev@vger.kernel.org, yi.zhu@intel.com, ipw2100-admin@linux.intel.com
Subject: Re: ieee80211 and devices which decrypt in hardware
Date: Thu, 14 Sep 2006 17:25:59 +0200 [thread overview]
Message-ID: <200609141725.59284.mb@bu3sch.de> (raw)
In-Reply-To: <450887B9.7080308@gentoo.org>
On Thursday 14 September 2006 00:35, Daniel Drake wrote:
> Michael Buesch wrote:
> > Does it strip ICV and FCS?
>
> The driver always strips FCS (unconditionally).
>
> The device does not strip ICV even when hardware decryption is in use,
> it gets included at the end of the frame, and I guess we should also
> handle that.
You should skb_trim it, or otherwise it will be included in the
payload, which will result in various weird bugs.
--
Greetings Michael.
prev parent reply other threads:[~2006-09-14 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 2:51 ieee80211 and devices which decrypt in hardware Daniel Drake
2006-09-13 14:27 ` Michael Buesch
2006-09-13 22:35 ` Daniel Drake
2006-09-13 22:43 ` Daniel Drake
2006-09-14 7:51 ` Johannes Berg
2006-09-14 15:25 ` Michael Buesch [this message]
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=200609141725.59284.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=dsd@gentoo.org \
--cc=ipw2100-admin@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=yi.zhu@intel.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).