[Bug 264238] WiFi stops working after upgrade from 13.0 to 13.1, AR9285
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #14 from Jaskie --- I can confirm now that network is still not work for the wireless network I reported. Do I close this bug or not? It do seem like compatibility issue with this specific network environment. I don't know how to dig more about this. I am thinking that I might just have to live with the fact that 13.1 just WON'T work for me. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Bug 264238] WiFi stops working after upgrade from 13.0 to 13.1, AR9285
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 J.R. Oldroyd changed: What|Removed |Added CC||f...@opal.com --- Comment #15 from J.R. Oldroyd --- (In reply to Jaskie from comment #14) I wouldn't close the PR until the problem is resolved. What you could do at this point is look at a detailed dump of the packets on both the working and the non-working systems. Do the tcpdump similar to what was proposed before: disable DHCP in /etc/rc.conf (ifconfig_wlan0="..." should not have DHCP in it) service netif stop wlan0 tcpdump -i wlan0 -w file.bpf -s 0 service netif start wlan0 then view using: tcpdump -r file.bpf -vvv port 67 or 68 Make sure that you're using the same bssid both times so that the comparison is useful (e.g., use a "bssid=xx:xx:xx:xx:xx:xx" in your wpa_supplicant.conf). There has to be some difference between what is sent. Or there has to be something blocking the DHCP datagrams from reaching the router. Or blocking the responses. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Bug 264238] WiFi stops working after upgrade from 13.0 to 13.1, AR9285
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #16 from Bjoern A. Zeeb --- (In reply to J.R. Oldroyd from comment #15) or some change in certain option handling now makes us send a bad request and 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 actually 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. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Bug 264238] WiFi stops working after upgrade from 13.0 to 13.1, AR9285
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #17 from Jaskie --- Created attachment 234405 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=234405&action=edit test files form 13.0 and 13.1 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Bug 264238] WiFi stops working after upgrade from 13.0 to 13.1, AR9285
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #18 from Jaskie --- So I have the same bssid in /etc/wpa_supplicant.conf, wlans_ath0="wlan0" ifconfig_wlan0="WPA" in /etc/rc.conf in both 13.0 and 13.1. Now I boot up 13.0 or 13.1 network is down and I have to run dhclient wlan0 to connect. I uploaded an attachment file. The two dmesg files are from fresh boot 13.0 and 13.1. Network was not working in both scenarios since DHCP was disabled. In 13.0, I boot up and run dhclient and then network is connected instantly % doas service netif stop wlan0 % doas tcpdump -i wlan0 -w file_13.0_working.bfp -s 0 tcpdump: wlan0: No such device exists (BIOCSETIF failed: Device not configured) So I had to % doas service netif start wlan0 % doas tcpdump -i wlan0 -w file_13.0_working.bfp -s 0 % doas dhclient wlan0 DHCPREQUEST on wlan0 to 255.255.255.255 port 67 DHCPACK from 10.134.255.254 bound to 10.134.132.85 -- renewal in 3600 seconds. % ping bing.com # get ping backs % Ctrl-C to stop tcpdump File is uploaded as file_13.0_working.bfp in attatchment. Then in fresh boot 13.1, network is down. % doas dhclient wlan0 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15 No DHCPOFFERS received. No working leases in persistent database - sleeping. % ping -c 3 bing @9:54 ping: Unknown host And from tcpdump I saw this: # tcpdump -i wlan0 -w file_13.1_NOT_working2.bfp -s 0 tcpdump: listening on wlan0, link-type EN10MB (Ethernet), capture size 262144 bytes 12 packets captured 12 packets received by filter 0 packets dropped by kernel Of course there is no active network. File is uploaded as file_13.1_NOT_working.bfp. I also tred /rescue/dhclient wlan0 same result, no network either. File is uploaded as file_13.1_NOT_working2.bfp. I hope this information helps. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Bug 264238] WiFi stops working after upgrade from 13.0 to 13.1, AR9285
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 Jaskie changed: What|Removed |Added Attachment #234405|0 |1 is obsolete|| --- Comment #19 from Jaskie --- Created attachment 234407 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=234407&action=edit Test file tarball form 13.0 and 13.1 This is a tarball (tar.gz) containing several files. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
