Date: Thu, 28 Apr 2022 01:44:10 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 263613] iwlwifi0 on framework laptop crashes when setting IP Message-ID: <bug-263613-21060-qteyN6Lpvx@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-263613-21060@https.bugs.freebsd.org/bugzilla/> References: <bug-263613-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=3D263613 --- Comment #8 from Jonathan Vasquez <jon@xyinn.org> --- Hey Chris, Thanks for that :). So I've been playing around with the system for the who= le day today trying to understand the behavior of this machine in conjunction = with FreeBSD and its drivers. There's just too many variables to explain everyth= ing but the good news is that with Chris' suggestion, DHCP now works on the iwlwifi0 adapter. DHCP doesn't work on the rwtn0 device though (I'm testing both to further test the interaction of the drivers and the hardware). All = the devices are working on Linux from the last time I tested them. Static IP assignment still crashes the iwlwifi0 device, and I was able to get Static = IP working in the rwtn0 device but it doesn't consistently work across -immedi= ate- reboots (I haven't tested more cold scenario since as I said, I was playing around with it for the whole day lol). Sometimes it takes 15 seconds for it= to work, sometimes it takes 45+ seconds, and something it just doesn't work.=20 There were also some other settings I was missing during static ip assignme= nt, specifically setting the: defaultrouter=3D"<ip>" field. I was able to test = this through /etc/rc.conf + service netif restart, and I also tried to manually construct the device and see if it worked. It basically yielded the above results. Example: ifconfig wlan0 create wlandev rwtn0 ifconfig wlan0 up ifconfig wlan0 scan (Shows the AP) wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf ---- On another terminal (tmux): ifconfig wlan0 inet 192.168.1.101 netmask 255.255.255.0 route add default 192.168.1.1 echo "nameserver 192.168.1.1" > /etc/resolv.conf ping 192.168.1.1 (No response, non-deterministic as above results described) netstat -rn and arp -a showed what you would expect in a correct working network (like the default gateway being set to 192.168.1.1 and the iface it used as wlan0). --- So yea, lots of different interactions here. I also noticed sometimes if I = left the "ifconfig_ue0=3D"DHCP" in the file, sometimes I wouldn't get a DHCP req= uest on the wireless card side.. but after many hours later I tried leaving both= of them enabled and it was still working fine.. so it could have just been some weirdness. I even rebooted my router just to make sure (even though everyth= ing was working, including multiple other machines connected to the same router= ). this is my current /etc/rc.conf for further info root@leslie:~ # cat /etc/rc.conf hostname=3D"leslie" dumpdev=3D"NO" zfs_enable=3D"YES" kld_list=3D"i915kms if_iwlwifi" devmatch_blacklist=3D"if_iwm" ifconfig_ue0=3D"DHCP" wlans_iwlwifi0=3D"wlan0" ifconfig_wlan0=3D"WPA SYNCDHCP" create_args_wlan0=3D"regdomain FCC country US" dbus_enable=3D"YES" ##### Other #wlans_rtwn0=3D"wlan0" #ifconfig_wlan0=3D"inet 192.168.1.101 netmask 255.255.255.0 ssid Summerland= WPA" #ifconfig_wlan0=3D"WPA SYNCDHCP" #defaultrouter=3D"192.168.1.1" Either way, at least we were able to find another bug (the static ip assign= ment on the iwlwifi0 card causes a crash). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263613-21060-qteyN6Lpvx>