From: Ping-Ke Shih <pkshih@realtek.com>
To: Viacheslav <adeep@lexina.in>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "Jernej Škrabec" <jernej.skrabec@gmail.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>
Subject: RE: rtw88: rtl8822cs AP mode not working
Date: Thu, 11 Jan 2024 00:42:11 +0000 [thread overview]
Message-ID: <0969b1ca039e423dbcc41de18db023c6@realtek.com> (raw)
In-Reply-To: <216e8522-fa56-4d54-ae32-74c6008a2075@lexina.in>
> -----Original Message-----
> From: Viacheslav <adeep@lexina.in>
> Sent: Wednesday, January 10, 2024 7:05 PM
> To: Ping-Ke Shih <pkshih@realtek.com>; linux-wireless@vger.kernel.org
> Cc: Jernej Škrabec <jernej.skrabec@gmail.com>; Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> Subject: Re: rtw88: rtl8822cs AP mode not working
>
> Hi!
>
> 10/01/2024 12.15, Ping-Ke Shih wrote:
> >
> >
> >> -----Original Message-----
> >> From: Viacheslav <adeep@lexina.in>
> >> Sent: Wednesday, January 10, 2024 3:07 PM
> >> To: linux-wireless@vger.kernel.org
> >> Cc: Ping-Ke Shih <pkshih@realtek.com>; Jernej Škrabec <jernej.skrabec@gmail.com>; Martin Blumenstingl
> >> <martin.blumenstingl@googlemail.com>
> >> Subject: rtw88: rtl8822cs AP mode not working
> >>
> >> Hello!
> >>
> >> We use RTL8822CS modules in our devices and we switched to rtw88 from an
> >> external driver by Realtek. Suddenly we discovered that the AP mode
> >> (hotspot) stopped working. The hotspot is set up, but it does not
> >> authorize client connections.
> >>
> >> In attacments log and config files.
> >>
> >> client - notebook with iwlwifi 0000:00:14.3: Detected Killer(R) Wi-Fi 6E
> >> AX1675i 160MHz Wireless Network Adapter (211NGW), REV=0x370
> >>
> >
> > It is probably because RTL8822CS doesn't issue beacon properly. Trying to
> > capture air packets will be helpful to clarify the problem.
>
> airdump-ng result in attachment.
> I don't see any captured beacon packets.
So, that is the problem. Did you see any weird messages in kernel log when
you were starting hostapd?
next prev parent reply other threads:[~2024-01-11 0:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 7:07 rtw88: rtl8822cs AP mode not working Viacheslav
2024-01-10 9:15 ` Ping-Ke Shih
2024-01-10 11:04 ` Viacheslav
2024-01-11 0:42 ` Ping-Ke Shih [this message]
2024-01-11 6:19 ` Viacheslav
2024-01-12 0:39 ` Ping-Ke Shih
2024-01-13 22:50 ` Martin Blumenstingl
2024-01-15 2:17 ` Ping-Ke Shih
2024-01-16 22:07 ` Martin Blumenstingl
2024-01-17 0:35 ` Ping-Ke Shih
2024-01-17 7:34 ` Sascha Hauer
2024-01-17 9:48 ` Viacheslav
2024-01-17 20:48 ` Martin Blumenstingl
2024-04-18 6:58 ` Gabriel Tisan
2024-04-18 10:55 ` Viacheslav
2024-05-06 9:38 ` Gabriel Tisan
2024-05-06 10:18 ` Viacheslav
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=0969b1ca039e423dbcc41de18db023c6@realtek.com \
--to=pkshih@realtek.com \
--cc=adeep@lexina.in \
--cc=jernej.skrabec@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
/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;
as well as URLs for NNTP newsgroup(s).