Berkeley Packet Filter

2012-09-16 Thread David Given
When trying to make wireless work on my eee 701, trying to ifup the interface produces: ifconfig: ioctl (SIOCAIFADDR): Invalid argument Can't attach interface ath0 to bpf device /dev/bpf0: No such device or address Failed to bring up ath0. /dev/bpf0 is present but doesn't appear as if there's a d

Re: Berkeley Packet Filter

2012-09-16 Thread Steven Chamberlain
Hi, On 16/09/12 12:54, David Given wrote: > ifconfig: ioctl (SIOCAIFADDR): Invalid argument > Can't attach interface ath0 to bpf device /dev/bpf0: No such device or > address > Failed to bring up ath0. You might see more clearly what ifup is doing with the -v switch. It looks like a different er

Re: Berkeley Packet Filter

2012-09-16 Thread Steven Chamberlain
On 16/09/12 12:54, David Given wrote: > [...] the config file in /boot/config-9.0-2-686 does not have a > 'device bpf' entry. I just noticed that file is merely a copy of the DEBIAN config file, so the includes are mentioned at the bottom, but they're not 'in-lined'. For the running kernel you ca

Re: Berkeley Packet Filter

2012-09-16 Thread David Given
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 t

Re: Berkeley Packet Filter

2012-09-16 Thread Steven Chamberlain
On 16/09/12 16:12, David Given wrote: [...] > 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=0x