Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <6c661903ad35a4619aeb8c642998b9f21883b0c1.camel@egauge.net>
Subject: Re: wilc1000: AP mode issue
From:   David Mosberger-Tang <davidm@egauge.net>
To:     Ajay.Kathat@microchip.com
Cc:     linux-wireless@vger.kernel.org
Date:   Tue, 11 Apr 2023 22:10:20 -0600
In-Reply-To: <bdd4f49a-213a-bf55-1c29-d74e56221795@microchip.com>
References: <e4cece9076cc9a5a4e4dbfa258a828eaec97e1af.camel@egauge.net>
         <bdd4f49a-213a-bf55-1c29-d74e56221795@microchip.com>
Organization: eGauge Systems LLC
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.44.4-0ubuntu1 
MIME-Version: 1.0
Precedence: bulk

On Wed, 2023-04-12 at 00:33 +0000, Ajay.Kathat@microchip.com wrote:
> Hi David,
>=20
> On 4/11/23 14:08, David Mosberger-Tang wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know =
the content is safe
> >=20
> > Ajay,
> >=20
> > I'm just starting to investigate an issue with the wilc1000 driver that=
 occurs
> > when it is operating as an access point.  I came across this thread:
>=20
> What is the issue observed with the AP mode.

I'm still working on simplifying the test case.  Right now, it's rather
complex:

 1) Connect wlan0 in managed mode to an existing access point.
 2) Create a virtual interface wlan0 (iw dev wlan0ap interface add
wlan0ap type __ap)
 3) Set up a captive portal on wlan0ap (iptables rules, web server,
dnsmasq)
 3) Start hostapd on wlan0ap

Once that's done, use a smartphone or any other client device to
connect to the captive portal's SSID.  The captive portal redirects any
HTTP requests to the portal's web server.

Now, when the client starts downloading pages from the web server,
something bad happens in the wilc1000.  The connections to the web
server get stuck and wilc1000 stops broadcasting the hostapd's SSID.
There are no error message (even with debug enabled in wilc1000).

Depending on the client device, the problems appears sooner or later.
For example, with Android 13, the problem happens infrequently but
with iOS or Android 9, it happens rather reliably and early on (within
the first few KiB of data transmission).

> >=20
> >   https://lore.kernel.org/linux-wireless/87pmkmylex.fsf@kernel.org/
> >=20
> > and was wondering if there has been progress towards converting the dri=
ver to
> > use the nl80211-based TX/RX interface.  If so, is this something that's
> > available somewhere or could be shared?
> >=20
>=20
> I haven't started working on this part yet. After completing few pending
> ongoing patches. I will look into this.

Great!

Best regards,

  --david