Results 1 to 5 of 5

Thread: A Pointer for Wireless Monitoring

  1. #1
    Junior Member
    Join Date
    Dec 2007
    Posts
    27

    Default A Pointer for Wireless Monitoring

    If you are like me, and happen to have an Atheros chipset (the majority of you have one from what I've been reading), don't bother stopping ath0 to put it into monitor mode. I have found success by starting a new interface in monitor mode (ath1). Just thought I'd share that one

  2. #2
    Junior Member duwey96's Avatar
    Join Date
    Nov 2007
    Posts
    41

    Default

    I've always started wifi0 using airmon-ng, and that creates a new interface ath1 in monitor mode.

  3. #3
    Junior Member
    Join Date
    Dec 2007
    Posts
    27

    Default

    Thats what I said to do

  4. #4

    Default

    ever wonder why the airmon-ng script can create a wlandev with the lowest appenix? exempli gratia: ath0, or if ath0 is up - ath1??

    if you were to simply do:
    wlanconfig ath create wlandev wifi0 wlanmode monitor

    I found that it uses the next appendix up from a cache somewhere..
    i can't figure out where but if i do that now, I get a VAP labeled ath61 or something.
    I mean, the extra digit isnt that much of a bother except when airmon-ng fails when i specify a channel number. Then i have to run iwconfig and see what the new appendix is, even though the tty dump from wlanconfig will say "ath0"

    happen to anyone else? I use madwifi-ng r2717. (stable enough for the internal wlan card of the MacBook late 2006)

  5. #5
    Developer
    Join Date
    Mar 2007
    Posts
    6,124

    Default

    I fail to see this as a tutorial. Moving to n00b section.

Posting Permissions

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