Date: Fri, 03 Jun 2022 16:40:04 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 264238] WiFi stops working after upgrade from 13.0 to 13.1, AR9285 Message-ID: <bug-264238-21060-9qQx9s4Wpd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264238-21060@https.bugs.freebsd.org/bugzilla/> References: <bug-264238-21060@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264238 Bjoern A. Zeeb <bz@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open --- Comment #27 from Bjoern A. Zeeb <bz@FreeBSD.org> --- In the 13.1 not-working case I see incoming TCP packets from the AP despite= you not having an IP address (assumed) given DHCP discover did not get a reply.= =20 There's also incoming ARP announcement from the AP-side; that somehow means the "network" knows where to find you (with your old IP address)? Given I have no insight in how complex this network is (is it just a residential router with builtin WiFi or more components) it is hard to say where to start looking. You should probably wait at least an ARP expiry timeout before running the = 2nd test. The other interesting bit would be: ifconfig wlan0 inet6 -ifdisabled accept_rtadv ping6 -n ff02::1%wlan0 ping6 -n ff02::2%wlan0 and see if you get replies in the non-working IPv4 case given there seems t= o be at least IPv6 link-local available on the RuiJieNe node. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264238-21060-9qQx9s4Wpd>