Date: Thu, 02 Jun 2022 16:31:39 +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-HL3vM6eHAf@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 --- Comment #16 from Bjoern A. Zeeb <bz@FreeBSD.org> --- (In reply to J.R. Oldroyd from comment #15) or some change in certain option handling now makes us send a bad request a= nd depending on server being more lenient or not .. It's like 5 changes changes in dhclient (if the issue is there): % git log --oneline freebsd/releng/13.0..freebsd/releng/13.1 sbin/dhclient/ 586827df60ce dhclient: support VID 0 (no vlan) decapsulation 75df39760ce0 dhclient: remove patching of static values in BPF programs 3bcf919c4e89 dhclient: skip_to_semi() consumes semicolon already 8751bff1a72e dhclient: support supersede statement for option 54 50ecd99be523 bpf: Add an ioctl to set the VLAN Priority on packets sent by = bpf I would highly prefer to have a binary tcpdump written to a file from both working and non-working setup. Not a textdump of such, so that we can actua= lly inspect packets. also I am tempted at this point to put this over to freebsd-net as it seems= it may not be a wireless issue given kernels can be interchanged (13.0 userland reported to work on 13.1 kernel) and we see associated. So it's unlikely a broad/multicast wifi problem. --=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-HL3vM6eHAf>