Date: Sat, 27 Feb 2016 21:22:00 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 207537] wireless does not associate properly - AR9565 Message-ID: <bug-207537-6-nX71ZXxZFo@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-207537-6@https.bugs.freebsd.org/bugzilla/> References: <bug-207537-6@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=3D207537 --- Comment #4 from Neil Tremble <ntremble@gmail.com> --- I subsequently commented out the wireless related lines in loader.conf and rc.conf, rebooting, then executing the commands manually: # kldload if_ath # ifconfig wlan0 create wlandev ath0 # wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf # dhclient wlan0 The kldload is not required as it says the module is already loaded or in t= he kernel. The ifconfig and wpa_supplicant commands appear to work properly. T= he dhclient command does not obtain an address. If I manually assign an addres= s: # ifconfig wlan0 inet 10.0.0.80 netmask 255.255.255.0 routing still fails. At one stage I noticed the association had gone, so I might need to do more there to get it to work at all. I'll keep trying to get it going with a static IP because I would like to be able to say for sure whether the issue is in the interface setup or just a dhclient thing. A static IP will do in the short term; if I can get that working at least my wireless will be usable. As it is my laptop is tied the the wired ethernet. --=20 You are receiving this mail because: 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-207537-6-nX71ZXxZFo>