public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Meduna <stano@meduna.org>
To: david@gibson.dropbear.id.au (David Gibson)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Orinoco_plx, WEP and 0.7.6 fw
Date: Sat, 20 Apr 2002 14:29:52 +0200 (CEST)	[thread overview]
Message-ID: <200204201229.g3KCTq407352@meduna.org> (raw)
In-Reply-To: <20020415032853.GK24053@zax> from "David Gibson" at apr 15, 2002 01:28:53

Hello,

> > I have the Siemens I-GATE 11M PCI card, which is a PrismII based
> > PCMCIA card in the PLX9052 PCI-PCMCIA adapter. This card has
> > firmware version 0.7.6 and definitely supports WEP - I am using
> > 128-bit WEP in Windows without problems.
> 
> The firmware supports WEP, but it is configured differently than
> version 0.8 and later, and I've never managed to work out how to
> properly activate it.

I looked at what does actually fail and have some interesting
datapoints. I used ethereal to watch two scenarios -

1. a communication between another client (a Pocket PC)
   and the access point/router and machines behind it

2. a communication between own machine and the AP

The failures seem to be connected with the data transmitted.
In the case 1 I had no problems to watch lengthy HTTP
communications. However I have never seen the POP request
going out (only answers).

Sometimes I got lenghty conversations also in the case 2, but
I also got a consistent failure mode - TCP checksum on the
receiving direction incorrect and exactly one byte garbled -
the last one. The resulting retry mostly had again the last byte
garbled, but to a different one. In one case the retry
succeeded and the following conversation was then flawless.

The failed packets were short (less than 256 bytes long), so this
is nothing that can be related to a fragment reassembling
or something like that.

That it is consistently the last byte that is garbled seems to
suggest some kind of off-by-one bug. Maybe in the driver,
maybe in the firmware...


What is the legal situation regarding RC4 now - can it be used
in the GPL software without risk, or is this still a grey area?
I think there is a possibility to do the WEP in software
(at least one source code I found does implement the encryption
to avoid the weak IVs) and I am probably going to set the
host en-/decrypt flags and give it a try. Would you accept
such (optional) patch?

Regards
-- 
                                   Stano


      reply	other threads:[~2002-04-20 12:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-13 19:21 Orinoco_plx, WEP and 0.7.6 fw Stanislav Meduna
2002-04-15  3:28 ` David Gibson
2002-04-20 12:29   ` Stanislav Meduna [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=200204201229.g3KCTq407352@meduna.org \
    --to=stano@meduna.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=linux-kernel@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