Page 2 of 2 FirstFirst 12
Results 11 to 18 of 18

Thread: Airpwn 1.4 injection

  1. #11
    Just burned his ISO
    Join Date
    Jan 2008
    Posts
    16

    Default

    root@bt: modprob ath_pci
    FATAL: Module ath_pci not found.

  2. #12
    Just burned his ISO
    Join Date
    Aug 2007
    Posts
    23

    Default

    You're using the wrong driver, based on my experience. I have a CiscoABG card (atheros) and I've ran into the same problem. Ff you read the airpwn site, you'll see they talk about people having success using the Atheros chipset, while its not officially supported, i believe

    In short, try using the '-d mac80211' command, AFTER running './mac80211_prep.sh'

    Because I'm not sure about everything, I had to download the 1.4 airpwn version to get the full scripts as I couldn't find them. I also couldn't do the install of 1.4 either (missing python2.4 dependencies?). 1.3 worked, but didn't support mac80211 drivers) The airpwn version on bt4 pre-final appears to be 1.4 but without the full directory....

    Like I said, just because I couldn't find it, it doesn't mean it's not there... I'm just an idiot

  3. #13
    Just burned his ISO
    Join Date
    Jan 2008
    Posts
    16

    Default

    Quote Originally Posted by dmshady001 View Post
    You're using the wrong driver, based on my experience. I have a CiscoABG card (atheros) and I've ran into the same problem. Ff you read the airpwn site, you'll see they talk about people having success using the Atheros chipset, while its not officially supported, i believe

    In short, try using the '-d mac80211' command, AFTER running './mac80211_prep.sh'

    Because I'm not sure about everything, I had to download the 1.4 airpwn version to get the full scripts as I couldn't find them. I also couldn't do the install of 1.4 either (missing python2.4 dependencies?). 1.3 worked, but didn't support mac80211 drivers) The airpwn version on bt4 pre-final appears to be 1.4 but without the full directory....

    Like I said, just because I couldn't find it, it doesn't mean it's not there... I'm just an idiot
    Idiot or not I greatly appreciate the reply. In backtrack 4 Beta my Wifi interface is ath0 which made me think that the madwifi driver was using ath_pci driver.

    Interface Chipset Driver
    wifi0 Atheros madwifi-ng
    ath0 Atheros Madwifi-ng VAP (parent: wifi0)

    root@bt:~# airdriver-ng loaded
    Found following stacks loaded (as module):

    Found following drivers loaded (as module):
    16. Madwifi[-ng] - IEEE80211
    Thats from BackTrack 4 Beta (before the pre-final)
    this is what I have in Pre-Final
    Interface Chipset Driver
    wlan0 Atheros Ath5k - [phy0]
    mon0 Atheros ath5k - [ph0]


    Found following stacks loaded (as module):
    2. mac80211

    Found following drivers loaded (as module):
    So thats what I have

  4. #14
    Just burned his ISO
    Join Date
    Aug 2007
    Posts
    23

    Default

    My card is external, so I had to modify the scripts to fit my needs (wlanx and monx)

    I'm able to get the app to SAY it injecting and and it's logging stuff. I've tried a couple different drivers in the command line. The problem I'm seeing it that it's only seeing one host. I'm outputting to the log and I'm not seeing my IP address.

    I've even moved it to a crappy netgear /b only device and I"m still not able to inject to that (however, the tool does show injections to all visible open networks.)

    I think it comes down to card support. Used to be Atheros cards were pretty good....

  5. #15
    Just burned his ISO
    Join Date
    Jan 2008
    Posts
    16

    Default

    Quote Originally Posted by dmshady001 View Post
    My card is external, so I had to modify the scripts to fit my needs (wlanx and monx)

    I'm able to get the app to SAY it injecting and and it's logging stuff. I've tried a couple different drivers in the command line. The problem I'm seeing it that it's only seeing one host. I'm outputting to the log and I'm not seeing my IP address.

    I've even moved it to a crappy netgear /b only device and I"m still not able to inject to that (however, the tool does show injections to all visible open networks.)

    I think it comes down to card support. Used to be Atheros cards were pretty good....
    Yea I got this netbook just because it had a Atheros chipset in it. Darren Kitchen from the show Hak5 uses the same netbook (well I think he uses the 8.9 Aspire One I use the 10.1 Aspire) And these cards do injection great. I use it all the time for IV agitation when cracking WEP keys
    aireplay-ng -3 -b AP_MAC_ADD -h MY_MAC_ADD ath0
    I think the problem is that BackTrack 4 Beta had the Madwifi-ng driver installed and loaded and thats why I get ath0 interface on that but Airpwn is not installed and I'm just epic fail when trying to install it.

    So I found out BackTrack 4 pre Final has Airpwn 1.4 already in there. I just create conf/content files and I should be good to go. Problem is I dont have the same Madwifi driver I had previously in the Beta of BT4. It's now using some ath5k driver instead. and as I showed previously it doesn't even show a driver loaded as a module it shows the mac80211 stack loaded as a module instead.

    I dunno *shrugs* I'm not giving up anytime soon tho.

  6. #16
    Just burned his ISO
    Join Date
    Jan 2008
    Posts
    16

    Default

    So after doing some research the ath5k driver that is installed is really shakey. I keep having problems with it. A friend of mine told me I should run ath9k but that doesnt even work. On top of that i read ath9k is for N cards which I do not have. Is there a way I can install the old madwifi driver? The ath_pci one? i've been looking around and I just need a point in the right direction

  7. #17
    Just burned his ISO
    Join Date
    Jan 2008
    Posts
    16

    Default

    So I found this post

    Keeping Backtrack up to date

    and figured i'd reinstall the old madwifi drivers right
    apt-get update
    apt-get upgrade && apt-get install madwifi-drivers r8187-drivers
    echo blacklist ath5k >> /etc/modprobe.d/blacklist # In case you want to use madwifi-ng as default
    So thats what I did.
    (btw did a fresh reinstall of BT4 PF just to be sure)

    So anyways then I rebooted and did iwconfig and low & behold

    wifi0 no wireless Extentions.

    ath0 IEE 802.11b ESSID:"" NICKNAME:""
    Mode: Managed Channel: 0 Access Point: Not-Associated
    Bit Rate: 0 kb/s Tx-Power:0 dBm Sensitivity=1/1
    Retryff RTS Thrff Fragment thrff
    Encryption Key: off
    Power Managementff
    Link Quality=0/70 Signal level=0 dBm Noise level=0 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0
    so i'm thinking good right? Not so much

    I do airmon-ng stop ath0 and I get
    Interface Chipset Driver
    wifi0 Atheros madwifi-ng
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *
    ath0 Atheros madwifi-ng VAP(parent: wifi0) (VAP destroyed)
    Ok WTF???? is with all the ieee80211_unref_mode: NULL iee80211_mode *'s??????

    So I do ifconfig wifi0 down & macchanger --mac AA:BB:CCD:EE:FF wifi0 followed by airmon-ng start wifi0

    and I get the following
    Interface Chipset Driver

    wifi0 Atheros madwifi-ngieee80211_unref_mode: NULL iee80211_mode *
    ieee80211_unref_mode: NULL iee80211_mode *

    ath0 Atheros madwifi-ng VAP (parent:wifi0)(monitor mode enabled)
    aireplay-ng --test ath0
    14:43:15 Trying broadcast probe requests....
    14:43:17 Injection is working!
    14:43:17 Found 2 APs

    14:43:17 Trying directed probe requests ....
    14:43:17 00:1C:10:A0:B0:59 - channel: 11 - 'HAS-NET'
    14:43:17 Ping (min/avg/max): 1.762mx/14.930ms/28.260ms Power: 39.17
    14:43:17 30/30: 100%

    14:43:17 00:18:01:98:0B:F9 - channel: 9 - 'leask'
    14:43:18 ping (min/avg/max): 1.721ms/3.078ms/10.370ms Power: 20.69
    14:43:18 20/30: 86%
    so I throw a quick /etc/init.d/wicd start and then startx so I can connect to HAS-NET and check my interweb connections

    Well it says No wireless networks found.

    so I throw a airmon-ng stop ath0 and a ifconfig wifi0 up and restart wicd /etc/init.d/wicd restart

    Now I get nothing in the wicd manager

  8. #18
    Just burned his ISO
    Join Date
    Jan 2008
    Posts
    16

    Default UPDATE: Diff Scenario

    Ok, So I've got a new netbook (Pile of crap btw) and I recently got my hands on a Alfa N (AWUS050NH) I installed the compat wireless drivers so my Alfa works with Aircrack using rt2800usb.

    What driver can I use for airpwn?

    I see rtl8180 rt2570 rt2500 rt73 rt61

    Do I just put '-d rt2800usb' or is the rt2800usb driver not supported by airpwn?

Page 2 of 2 FirstFirst 12

Posting Permissions

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