Quote:
|
Originally Posted by renderman
The ioctl is probobly related to the dynamic creation of the 'prism0' interface. Make sure your issuing the 'wl ap 0' command before you fire up the drone. The drone will only work if it's in Client mode.
My suggestion would be to step through the commands in the rundrone.sh script, then try running the drone with a '&' at the end, so that after you connect with kismet, run 'wl scan' and see if it scans.
The other thing to check is the indents in scanme.sh, make sure that the 2 lines after 'do' are indented
|
Well, this is just weird because it worked before, and after rebooting the router I'm getting the error now.
When I run through the commands in the rundrone.sh script:
'wl ap 0'
'wl disassoc' returns "eth1: Invalid argument, Disassociate from the current BSS/IBSS."
'wl passive 1'
'wl promisc 1'
'chmod 777 /usr/bin/kismet*'
'usr/bin/./kismet_drone -f /etc/kismet_drone.conf &' returns the same
FATAL: iotcl: No such device error.
It seems to me like I must be messing something up in the kismet_drone.conf file.
Edit: I started over from scratch with the kismet_drone install, but same results. So close...
Edit part 2: When I changed "eth1" to "eth0" the drone starts up (albeit with some errors) and I can connect to it from my laptop. It does see my wireless network. However, it is still not scanning. I ran the drone with &, and tried 'wl scan' but no luck there.