Date: Fri, 24 Jun 2011 20:07:19 -1000 From: Kevin Oberman <kob6558@gmail.com> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-wireless@freebsd.org Subject: Re: Couldn't connect to wireless networking Message-ID: <BANLkTimzhBq7MyVv64LnEbQ1i44%2BGgcPhA@mail.gmail.com> In-Reply-To: <BANLkTikHY-tKG3UL5pVMqqyTQ1ubb9GOoQ@mail.gmail.com> References: <BANLkTinNhA12Z2ar6mUapNQfXwJn1aRDew@mail.gmail.com> <BANLkTikHY-tKG3UL5pVMqqyTQ1ubb9GOoQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2011/6/24 Adrian Chadd <adrian@freebsd.org>:
> Hi!
>
> You've not really posted enough information.
>
> * Has the system created a wlan0 interface?
> * is wpa_supplicant running on the wlan0 or ath0 interface? (the
> rc.conf script looks right, but I've not tried it myself to verify.)
>
> Thanks,
>
>
> Adrian
>
> 2011/6/25 =D7=DD=BA=E1=CC=EC=CF=C2 <zhtx10@gmail.com>:
>> Hi, all.
>>
>> Last week, I moved from Fedora to FreeBSD.
>> Then, I try to connect to wireless networking (wifi).
>> I did some things like handbook, but it showed me:
>> ---------
>> # /etc/rc.d/netif start
>> Starting wpa_supplicant.
>> ioctl [SIOCG80211, op98, len 32]: Invalid argument
>> ELOOP: remaining socket: sock=3D5, eloop_data=3D0x800e0b1c0
>> user_data=3D0x800e070f0 handler =3D0x421840
>> /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant
>> ifconfig: create: bad value
>> Starting Network: lo0 ath0
>> lo: .....
>> ath0: ....
>> status: no carrier
>> ---------
>>
>> I don't know what i did wrong.
>> This is my rc.conf:
>> ---------
>> hostname=3D"laptop.mike"
>>
>> wlans_ath0=3D"wlan0"
>> ifconfig_ath0=3D"WPA DHCP"
>> ---------
>>
>> This is my wpa_supplicant.conf:
>> ---------
>> network {
>> ssid=3D"WEB"
>> psk=3D"12345678"
>> }
>> ---------
>>
>> btw. how to enable snd_driver when FreeBSD starts?
>>
I think his main problem is that he is trying to configure ath0
instead of wlan0.
I see this quite often and felt that, last time I read it, the
documentation was nit very clear on this.
I might also mention that adding 'snd_hda_load=3D"YES"' to
/boot/loader.conf will probably take care of the sound issue, assuming
he has HDA audio like almost all modern system do unless an add-on
audio card is installed. (Not that this is on-topic for this list.)
--=20
R. Kevin Oberman, Network Engineer - Retired
E-mail: kob6558@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTimzhBq7MyVv64LnEbQ1i44%2BGgcPhA>