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
Date: Mon, 16 Aug 2021 00:45:38 +0000 [thread overview]
Message-ID: <5996f62cd8594a4d98490a8ad76a61a7@realtek.com> (raw)
In-Reply-To: <3b903f001e13429d81cb12d78b396ce5@realtek.com>
> -----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
prev parent reply other threads:[~2021-08-16 0:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 0:51 Difficulty connecting to AP using rtw89 Larry Finger
2021-07-16 3:17 ` Pkshih
2021-07-16 16:40 ` Larry Finger
2021-07-17 1:40 ` Pkshih
2021-07-17 9:39 ` Larry Finger
2021-07-19 2:44 ` Pkshih
2021-08-06 20:18 ` Jan Reusch
2021-08-09 5:52 ` Pkshih
2021-08-16 0:45 ` Pkshih [this message]
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=5996f62cd8594a4d98490a8ad76a61a7@realtek.com \
--to=pkshih@realtek.com \
--cc=jan@jreusch.de \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.