Results 1 to 6 of 6

Thread: Why do I have soo many Interfaces - wifi0, wlan0, ath0 and ath1?

  1. #1
    Just burned his ISO
    Join Date
    Mar 2010
    Posts
    23

    Question Why do I have soo many Interfaces - wifi0, wlan0, ath0 and ath1?

    Hello everyone,

    I have two wireless cards in my Dell Inspiron E1505.

    - built-in Intel WiFi Link 4965 AGN
    - D-Link DWA-643 Xtreme N Expresscard

    Being that the 4965 does not support injection, I decided to purchase the DWA-643 and give it a try, as it should be supported per the following link: hxxp://aircrack-ng.org/doku.php?id=compatibility_drivers#compatibility

    Whenever I run airmon-ng, I get the following list:

    Interface Chipset Driver

    wifi0 Atheros madwifi-ng
    wlan0 Intel 4965 a/b/g/n iwl4965 - [phy0]
    ath0 Atheros madwifi-ng VAP (parent: wifi0)


    Why do I have two interfaces for the D-Link card and what's the difference?

    Here's what i get when I try to put ath0 in monitor mode:
    bt ~ # airmon-ng start ath0

    Interface Chipset Driver

    wifi0 Atheros madwifi-ng
    wlan0 Intel 4965 a/b/g/n iwl4965 - [phy0]
    ath0 Atheros madwifi-ng VAP (parent: wifi0) (VAP cannot be put in monitor mode)


    Now this is what I get when I try to put wifi0 in monitor mode:
    bt ~ # airmon-ng start wifi0


    Interface Chipset Driver

    wifi0 Atheros madwifi-ng
    wlan0 Intel 4965 a/b/g/n iwl4965 - [phy0]
    ath0 Atheros madwifi-ng VAP (parent: wifi0)
    ath1 Atheros madwifi-ng VAP (parent: wifi0) (monitor mode enabled)

    As you can see... I now have ath1 - why so many interfaces? Can someone please help me understand what's going on and which will I be using in airodump-ng?

    Thank you all in advance.

  2. #2
    My life is this forum Barry's Avatar
    Join Date
    Jan 2010
    Posts
    3,817

    Default

    Quote Originally Posted by Newbie_from_NJ View Post
    Hello everyone,

    I have two wireless cards in my Dell Inspiron E1505.

    - built-in Intel WiFi Link 4965 AGN
    - D-Link DWA-643 Xtreme N Expresscard

    Being that the 4965 does not support injection, I decided to purchase the DWA-643 and give it a try, as it should be supported per the following link: hxxp://aircrack-ng.org/doku.php?id=compatibility_drivers#compatibility

    Whenever I run airmon-ng, I get the following list:

    Interface Chipset Driver

    wifi0 Atheros madwifi-ng
    wlan0 Intel 4965 a/b/g/n iwl4965 - [phy0]
    ath0 Atheros madwifi-ng VAP (parent: wifi0)


    Why do I have two interfaces for the D-Link card and what's the difference?

    Here's what i get when I try to put ath0 in monitor mode:
    bt ~ # airmon-ng start ath0

    Interface Chipset Driver

    wifi0 Atheros madwifi-ng
    wlan0 Intel 4965 a/b/g/n iwl4965 - [phy0]
    ath0 Atheros madwifi-ng VAP (parent: wifi0) (VAP cannot be put in monitor mode)


    Now this is what I get when I try to put wifi0 in monitor mode:
    bt ~ # airmon-ng start wifi0


    Interface Chipset Driver

    wifi0 Atheros madwifi-ng
    wlan0 Intel 4965 a/b/g/n iwl4965 - [phy0]
    ath0 Atheros madwifi-ng VAP (parent: wifi0)
    ath1 Atheros madwifi-ng VAP (parent: wifi0) (monitor mode enabled)

    As you can see... I now have ath1 - why so many interfaces? Can someone please help me understand what's going on and which will I be using in airodump-ng?

    Thank you all in advance.

    Atheros based devices have what are called virtual devices. Your hardware will be wifiX and the device will be athX. Usually you'll want to destroy the non-monitor virtual device before creating the monitor mode device.
    Of course, if you really wanted to have some fun, go to Wal-Mart late at night and ask the greeter if they could help you find trashbags, roll of carpet, rope, quicklime, clorox and a shovel. See if they give you any strange looks. --Streaker69

  3. #3
    Junior Member rumenovski's Avatar
    Join Date
    Dec 2008
    Posts
    29

    Default

    To enable monitor mode use this
    bt ~ # airmon-ng stop ath0
    bt ~ # airmon-ng start wifi0
    now you have ath0 in monitor mode
    To go back in managed mode use:
    bt ~ # airmon-ng stop ath0
    bt ~ # wlanconfig ath create wlandev wifi0 wlanmode managed

  4. #4
    Just burned his ISO
    Join Date
    Mar 2010
    Posts
    23

    Thumbs up

    Quote Originally Posted by rumenovski View Post
    To enable monitor mode use this
    bt ~ # airmon-ng stop ath0
    bt ~ # airmon-ng start wifi0
    now you have ath0 in monitor mode
    To go back in managed mode use:
    bt ~ # airmon-ng stop ath0
    bt ~ # wlanconfig ath create wlandev wifi0 wlanmode managed
    Thank you. Above worked Flawlessly!

  5. #5
    Junior Member rumenovski's Avatar
    Join Date
    Dec 2008
    Posts
    29

    Default

    You are welcome

  6. #6
    Just burned his ISO
    Join Date
    Apr 2009
    Posts
    1

    Default

    I have this problem:


    cristina@ubuntu:~$ sudo airmon-ng stop ath0

    Interface Chipset Driver

    wifi0 Atheros madwifi-ng
    ath0 Atheros madwifi-ng VAP (parent: wifi0) (VAP destroyed)

    cristina@ubuntu:~$ sudo airmon-ng start wifi0


    Interface Chipset Driver

    wifi0 Atheros madwifi-ngError for wireless request "Set Frequency" (8B04) :
    SET failed on device ath0 ; No such device.
    ath0: ERROR while getting interface flags: No such device

    ath1 Atheros madwifi-ng VAP (parent: wifi0)

    And the only way to restore the connection is reboot.

Posting Permissions

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