Originally Posted by kirmet
wlanconfig ath1 destroy
seems it's allready up when you get that error...
On a side note to what he said I have found that ath0 prefers to be the in the "Managed" mode at all times. Use ath1 for monitor mode.
yah that was the question ... i know you can create differnt kind of virt. interface one AFTER another but you cant run 2 different interface like
Originally Posted by duxzero
ath0 in monitor mode and
ath1 in ap mode or?
perhaps i just didnt understand something right here.
You have lost me my friend, just take a brief moment to further explain your problem. More details on the inital question is a good start. Based on what information you have given thus far I feel I may have a solution to your problem but I don't want to be giving you false information so if you could supply me supplemental information Ill decide if my soultion is compatable with your problem.
As far as I can see it does not work that way. You ether use ath1 or ath0 but if you have ath1 in monitor mode you cant use ath0 till ath1 is destroyed. I know it gets a little crazy creating the vwlan adapters to use onitor mode but a simple script should make it easy on you.
Do you really need to destroy it or is it enough to ifconfig ath0 down?
Thanks for the instructions, I followed them and am up and surveying fine.
I am having an issue with injecting, as seems to be the case with several folks and madwifi-ng.
I can run kismet/airodump without issue, but when I launch aireplay, it appears to not see the driver
ioctl (SIOCGIFINDEX) failed: no such device.
I have used the wlanconfig commands to bring up a second interface (ath1) instead of just using ath0 and it doesnt seem to work either.
I have googled out the wazoo and have seen numerous issues, but not really this one.
here is the commands run
wlanconfig ath0 destroy
wlanconfig ath0 create wlandev wifi0 wlanmode monitor
airodump ath0 file 0 (succeeds)
in a new window
aireplay -0 -x 120 -b MAC ath0
then it generates the error above.
I have also tried aireplay-ng - and it generates the same message, so I either have something configured wrong, or my patch is not applied correctly.
Anyone have input as far as troubleshooting?
Thanks in advance