From: David Gibson <david@gibson.dropbear.id.au>
To: Stanislav Meduna <stano@meduna.org>
Cc: jt@hpl.hp.com, linux-kernel@vger.kernel.org
Subject: Re: Orinoco_plx, WEP and 0.7.6 fw
Date: Mon, 15 Apr 2002 13:28:53 +1000 [thread overview]
Message-ID: <20020415032853.GK24053@zax> (raw)
In-Reply-To: <200204131921.g3DJLHw02324@meduna.org>
On Sat, Apr 13, 2002 at 09:21:17PM +0200, Stanislav Meduna wrote:
> Hello,
>
> the file drivers/net/wireless/orinoco.c in 2.4.17 contains
> on the line 1424:
>
> priv->has_wep = (firmver >= 0x00008);
>
> 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.
> If I change the line to enable the WEP for fw 7, I get mixed
> results in 2.4.19-pre6:
>
> - I can ping, but I cannot telnet.
> - My dmesg is full of
> eth1: Null event in orinoco_interrupt!
That's unrelated, due to a shared interrupt.
> and ocassionally I get
> eth1: Undecryptable frame on Rx. Frame dropped.
> - when I ping I seem to get double replies sometimes (depending
> on who I ping - never for the access point, always for another
> client) - either I am somehow seeing both the packet from
> the client to the AP and from AP to me, or there is some
> problem in the receiving routines
>
> Does the driver support interrupt sharing? I have quite a lot
> devices on the PCI bus, the plx board is not able to get
> a dedicated interrupt and shares it with the USB controller.
> I have a SMP board, which can be a factor too.
Yes it does, except for that "Null event" message which is gone in
more recent versions (not yet pushed to Linus and Marcelo).
> Anyway, if I can ping and see the traffic of another clients
> using tcpdump, the has_wep check is obviously too strict.
> I would suggest to either lower the requirement to firmware 7,
> or (if this is an exception and another cards are different)
> to add a module parameter to override it.
Yes, but the interface doesn't actually work properly.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson
next prev parent reply other threads:[~2002-04-15 3:29 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 [this message]
2002-04-20 12:29 ` Stanislav Meduna
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=20020415032853.GK24053@zax \
--to=david@gibson.dropbear.id.au \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stano@meduna.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