From: Johannes Berg <johannes@sipsolutions.net>
To: Peter.T.Breuer@gmail.com, linux-wireless@vger.kernel.org
Subject: Re: ipw2200 driver no longer sets encrypted WEP in ipw2200 device?
Date: Sun, 13 Jun 2021 21:19:30 +0200 [thread overview]
Message-ID: <d04aa1e0550572448f2443c763ddc0260fabcd3c.camel@sipsolutions.net> (raw)
In-Reply-To: <20210613103347.0c2148bd@ptb> (sfid-20210613_113416_435859_DECC4D0A)
On Sun, 2021-06-13 at 10:33 +0100, Peter Breuer wrote:
> This list is so offically dead! Still, I have a clue for you:
You sound frustrated. FYI, in case you haven't noticed, the list isn't
even near dead. I'll have a clue down below as to why your question
didn't get any answers.
> On Thu, 10 Jun 2021 13:11:39 +0100
> Peter Breuer <Peter.T.Breuer@gmail.com> wrote:
>
> > Hello - has somebody disabled encrypted WEP in ipw2200 firmwares, or
> > done something global that would have an equivalent effect, perhaps
>
> Same issue with WPA1 or 2. Plaintext is OK except the signal keeps
> dropping, and the same is true even from my modern mobile phone.
>
> The clue is this note from TP-Link:
>
> https://www.tp-link.com/en/support/faq/2303/
Which is talking about the 7265 as the oldest product of the bunch, and
~9260 as the newest.
Those had a launch date of Q3'14 and Q4'17 respectively. You might call
them old, but evidently they were fixed. I can't even speculate what the
issue might have been though, but if it wasn't just a Windows driver
(Linux not affected) or firmware issue (new binaries would've been
released for Linux as well), then I certainly never heard about it.
However, your thread here is talking about ipw2200. The devices that
driver is for aren't even listed on ark.intel.com (any more?), but I
recently du out something about them for unrelated reasons. The _latest_
of the bunch (this driver works on) was a mini-PCI (not PCIe) product
called 2915ABG, with a *launch* date of ~2003, and an *EOL* date of EOY
2009.
I think you'll not be surprised that there's hardly anyone who could
help you.
I'll note though that the driver for those ancient devices is just as
ancient, and (obviously) hasn't changed recently. You'll need to look
elsewhere.
I'm also not sure why you're complaining about WEP (might as well run
open network) and AX interoperability together. :)
johannes
prev parent reply other threads:[~2021-06-13 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 12:11 ipw2200 driver no longer sets encrypted WEP in ipw2200 device? Peter Breuer
2021-06-13 9:33 ` Peter Breuer
2021-06-13 19:19 ` Johannes Berg [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=d04aa1e0550572448f2443c763ddc0260fabcd3c.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Peter.T.Breuer@gmail.com \
--cc=linux-wireless@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