Results 1 to 5 of 5

Thread: airmon-ng -> VAP destroyed

  1. #1
    Just burned his ISO
    Join Date
    Jun 2008
    Posts
    21

    Default airmon-ng -> VAP destroyed

    I've got a problem with backtrack 3 that I can't resolve. my wireless card is a Netgear WPN311 pci, which according to backtrack should work right out of the box. The instructions I've read tell me:
    airmon-ng
    I get:
    Interface Chipset Driver
    wifi0 Atheros madwifi-ng
    ath0 Atheros madwifi-ng VAP (parent: wifi0)
    I don't understand why I get two items when I think I should get one.
    Further instructions say:
    airmon-ng stop ath0.
    Everyone else gets a message that their device is disabled. I get:
    Interface Chipset Driver
    wifi0 Atheros madwifi-ng
    ath0 Atheros madwifi-ng VAP (parent: wifi0) (VAP destroyed)
    - notice the end - (VAP destroyed) and I can't do a thing with it after that.
    I can do
    ifconfig ath0 down
    and
    macchanger --mac
    but if I do:
    airmon-ng start ath0 all I get back is:
    Interface Chipset Driver
    wifi0 Atheros madwifi-ng
    and if I do
    airodump-ng ath0I get
    Interface ath0:
    ioctl(SIOCGIFINDEX) failed: No such device
    thanks for any help, this is driving me nuts.
    In your response please bear in mind I'm newbie to linux and I find even the simple things puzzling. Thanks.

  2. #2
    Senior Member
    Join Date
    Apr 2008
    Posts
    2,008

    Default

    Try entering WPN311 into the search box. I ensure you that you will find several posts that will clear your problem right up.

    If you after this research still are unable to figure out the solution feel free to post back and we will try to help you out.
    -Monkeys are like nature's humans.

  3. #3
    Just burned his ISO
    Join Date
    Jun 2008
    Posts
    21

    Default

    ok thanks tron. I did make some progress. I worked out how to get the ath0 back from the dead by going:
    airmon-ng stop ath0 (VAP destroyed)
    airmon-ng start ath0 ( wifi0 there but no ath0 though....)
    ifconfig
    airmon-ng start wifi0 (ath0 monitor mode enabled)
    airmon-ng start ath0 (VAP not in monitor mode)
    ifconfig ath0 up
    airmon-ng (VAP parent wifi0)
    airodump ath0 ---> now works

    I'm sure this is probably a really amateur dumb way to do it but it worked for me.

  4. #4
    Member m1cha3l's Avatar
    Join Date
    May 2008
    Posts
    208

    Default

    all you should need is

    Code:
    airmon-ng stop ath0
    then
    Code:
    airmon-ng start wifi0
    this should make the next command work fine
    Code:
    airodump-ng ath0

  5. #5
    Just burned his ISO
    Join Date
    May 2009
    Posts
    4

    Default aireplay -1 0 -a bssid -h fake mac not working the second time.....

    Hello! I have used the above command with success the first time but when I tried it the second time, I had the same problem as the other person with the following statement of my ath0 driver being VAP destroyed. I also did airmon-ng stop ath0 and airmon-ng start wifi0 which work as I could then use airodump-ng ath0 to find all the bssids. I just like to know why I couldn't get packet injection to work the second time as it did work the first time. My card is fully supported so that is no problem. I have also heard that it does not support some APs. Thanks!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •