On 16/09/12 13:12, Steven Chamberlain wrote:
[...]
> You might see more clearly what ifup is doing with the -v switch.
>
> It looks like a different error happens first.
Yep; turns out that dhclient is failing because the device has failed to
be initialised because wpa-supplicant is confused. I think the BPF error
is a red herring.
The reason it's confused is because ifup assumes that if you don't
specify a wpa-driver clause it should use wext, which of course the
FreeBSD kernel doesn't support. Setting the driver to bsd now produces
the following:
wpa_supplicant[2036]: ioctl[SIOCS80211, op=16, arg_len=0]: Invalid argument
wpa_supplicant[2036]: ath0: Failed to initialize driver interface
wpa_supplicant[2036]: ELOOP: remaining socket: sock=5
eloop_data=0x8122178 user_data=0x8122530 handler=0x80dc1e0
As a wild stab in the dark --- how is firmware handled on kFreeBSD? I
have firmware-atheros installed; will it be loaded automatically or do I
need to do it manually?
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
│
│ life←{ ↑1 ⍵∨.^3 4=+/,¯1 0 1∘.⊖¯1 0 1∘.⌽⊂⍵ }
│ --- Conway's Game Of Life, in one line of APL
Attachment:
signature.asc
Description: OpenPGP digital signature