Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Peter Breuer <peter.t.breuer@gmail.com>
Date:   Sun, 13 Jun 2021 10:33:47 +0100
To:     linux-wireless@vger.kernel.org
Subject: Re: ipw2200 driver no longer sets encrypted WEP in ipw2200 device?
Message-ID: <20210613103347.0c2148bd@ptb>
In-Reply-To: <20210610131139.4fce5404@ptb>
References: <20210610131139.4fce5404@ptb>
Reply-To: Peter.T.Breuer@gmail.com
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

This list is so offically dead! Still, I have a clue for you:

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/
  TP-Link has officially begun to launch our 802.11AX class wireless
  routers.  However, some Intel WLAN adapters with old driver can't
  detect the wireless signal of our routers.  Please upgrade the driver
  of your WLAN card to the latest if you have this issue.

  Intel has also released a FAQ for its compatibility issue:
  https://www.intel.com/content/www/us/en/support/articles/000054799/network-and-i-o/wireless-networking.html

I imagine the issue is broad (TP-Link would downplay it) and might be a
major messup.  Blame Intel for not predicting your future mistake ,
would you ..  heh heh and see what happens.

Has anything of these Intel driver changes made it into a recent kernel?

See where brand loyalty gets you ...

PTB