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;
Authenticated-By: 
From:   Pkshih <pkshih@realtek.com>
To:     Pkshih <pkshih@realtek.com>, Jan Reusch <jan@jreusch.de>,
        "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: Difficulty connecting to AP using rtw89
Thread-Topic: Difficulty connecting to AP using rtw89
Thread-Index: AQHXedzEvSHwSXSC2EGxNTyUmGxj/atE4CcwgABoiACAARvNsIAAARaAgAM0tpCAHOxcgIAER3XAgAqsXPA=
Date:   Mon, 16 Aug 2021 00:45:38 +0000
Message-ID: <5996f62cd8594a4d98490a8ad76a61a7@realtek.com>
References: <2551f3d4aff248e29118a2c6339e4d96@realtek.com>
 <YQ2ZHTCCzbXil+9Y@akk.org> <3b903f001e13429d81cb12d78b396ce5@realtek.com>
In-Reply-To: <3b903f001e13429d81cb12d78b396ce5@realtek.com>
Accept-Language: en-US, zh-TW
Content-Language: zh-TW
x-kse-attachmentfiltering-interceptor-info: no applicable attachment filtering
 rules found
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: =?us-ascii?Q?Clean,_bases:_2021/8/15_=3F=3F_03:30:00?=
x-kse-bulkmessagesfiltering-scan-result: protection disabled
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
X-KSE-ServerInfo: RTEXH36502.realtek.com.tw, 9
X-KSE-Attachment-Filter-Triggered-Rules: Clean
X-KSE-Attachment-Filter-Triggered-Filters: Clean
X-KSE-BulkMessagesFiltering-Scan-Result: protection disabled
X-KSE-AntiSpam-Outbound-Interceptor-Info: scan successful
X-KSE-AntiSpam-Version: 5.9.20, Database issued on: 08/16/2021 00:33:18
X-KSE-AntiSpam-Status: KAS_STATUS_NOT_DETECTED
X-KSE-AntiSpam-Method: none
X-KSE-AntiSpam-Rate: 30
X-KSE-AntiSpam-Info: Lua profiles 165565 [Aug 16 2021]
X-KSE-AntiSpam-Info: Version: 5.9.20.0
X-KSE-AntiSpam-Info: Envelope from: pkshih@realtek.com
X-KSE-AntiSpam-Info: LuaCore: 454 454 39c6e442fd417993330528e7f9d13ac1bf7fdf8c
X-KSE-AntiSpam-Info: {Prob_susp_to_in_reply, in_rep}
X-KSE-AntiSpam-Info: {Tracking_uf_ne_domains}
X-KSE-AntiSpam-Info: d41d8cd98f00b204e9800998ecf8427e.com:7.1.1;realtek.com:7.1.1;github.com:7.1.1;127.0.0.199:7.1.2
X-KSE-AntiSpam-Info: Rate: 30
X-KSE-AntiSpam-Info: Status: not_detected
X-KSE-AntiSpam-Info: Method: none
X-KSE-AntiSpam-Info: Auth:dkim=none
X-KSE-Antiphishing-Info: Clean
X-KSE-Antiphishing-ScanningType: Heuristic
X-KSE-Antiphishing-Method: None
X-KSE-Antiphishing-Bases: 08/16/2021 00:35:00
Precedence: bulk
List-ID: <linux-wireless.vger.kernel.org>
X-Mailing-List: linux-wireless@vger.kernel.org


> -----Original Message-----
> From: Pkshih [mailto:pkshih@realtek.com]
> Sent: Monday, August 09, 2021 1:52 PM
> To: Jan Reusch; linux-wireless@vger.kernel.org
> Subject: RE: Difficulty connecting to AP using rtw89
> 
> > -----Original Message-----
> > From: Jan Reusch [mailto:jan@jreusch.de]
> > Sent: Saturday, August 07, 2021 4:19 AM
> > To: linux-wireless@vger.kernel.org; Pkshih
> > Subject: RE: Difficulty connecting to AP using rtw89
> >
> > Hey hey
> > Hope this works and gets sorted right, i had to manually set the
> > in-reply-to header.
> >
> > I'm one of the people having problems with ipv6 and the rtw89 driver.
> > i've tested it with the debian bullseye kernel and vanilla 5.13 from
> > kernel.org
> >
> > It's about a Realtek 8852 in a Thinkpad E14 Gen2 (amd).
> >
> > > > The driver handles L2 things only, but IPv6 that is L3 that we don't
> > > > have special deal.
> > > > Could I know the problem you met?
> >
> > Yep that was also my first reaction 1:1, but it's 100% repdoducible.
> > Ethernet connection works, i get an v4 adress and an v6 one (SLAAC), it
> > works flawlessly with an USB wifi stick, but the integrated wifi only
> > gets the link local ipv6 address,  an ipv4 one but nothing more.
> > I've tried to dump router advertisements, but none of them pop up. (As
> > soon as i attach the ethernet cable/usb wifi stick they're there...)
> 
> Could you provide your dump of USB wifi stick and rtw89?
> If possible, I'd like to have tcpdump of interfaces locally and sniffer
> packets in the air. Then, I can check the good and bad cases, and check
> if any transmitting data is eaten by rtw89.
> 

With Jan's help, we get this fixed.
This fix will be included in next submission recently. If people want this
fix right now, please checkout Larry's GitHub https://github.com/lwfinger/rtw89

Ping-Ke