RE: rtw88 multicast failure in AP mode

[Ping-Ke Shih <pkshih@realtek.com>]

Marcin Ślusarz <marcin.slusarz@gmail.com> wrote:
> Let's assume we have 3 systems: A and B use 8821CU chip, and C uses
> another chip from a different vendor.
> 
> If A is in AP mode and A and B use the rtw88 driver, pinging A from B
> and C by local name doesn't work because name resolution fails: avahi
> on B and C sends a multicast request to resolve A.local, A sees it and
> responds, but neither B nor C sees the response.
> 
> In the same situation, but with A and B using the rtl8821cu driver
> (from https://github.com/morrownr/8821cu-20210916.git), everything
> works - B and C see A's response and can resolve A.local.
> 
> If C is in AP mode, resolving C from A and B also works.
> 
> This leads me to believe there's something wrong with rtw88 when
> sending multicast packets in AP mode.

Have you captured air packets sent by C (AP mode)? (To check if TX properly.)

Have you tried non-secure connection? (To check if encryption properly.)

I think this can help to address problem.