Results 1 to 4 of 4

Thread: aireplay-ng problem

  1. #1
    Just burned his ISO
    Join Date
    Mar 2006
    Posts
    1

    Default aireplay-ng problem

    Hello I'm trying to test my methods on my own wireless router in WEP mode.
    I am using the original Backtrack 4 release version posted in the downloads section not R1 or R2 as R2 would not even see the wireless card at all.
    I've installed it on a boot-able flash stick with no issues.
    I have a laptop with a Intel 2200BG chipset and have never been able to get a definitive answer about whether or not it can do injection with the ipw2200 driver supplied with backtrack 4, the dates of all the other posts are fairly old and refer to changes needed in the driver, and some say no changes needed for injection.
    I search all over the web using Google and keep getting sent back to this site and here all past post about similar issues, all tell the poster that he should search better and that they basically are not very smart for not searching Google. One big circle.
    here is what I've tried so far and the progress I've made.
    start with airmon-ng and found that the wireless card on this laptop is ID'ed as eth1.
    I have found this is very common for this card and is of no worry.
    So I use, airmon-ng start eth1
    and get this response. interface eth1 chipset Intel 2200BG Driver ipw2200(monitor mode enabled)
    I leave this window open and start a new terminal.
    then I confirm my test signal from my home router with airodump-ng eth1

    After confirming that I am receiving many AP's along with my test AP I then
    use airodump-ng --bssid xx:xx:xx:xx:xx:xx --channel 6 --ivs -w mytestssid eth1

    I start seeing beacons and data counting up, data counting up slowly.
    I then leave this open and open another terminal and use aireplay-ng -5 -b xx:xx:xx:xx:xx:xx eth1.

    I get this response
    No answer, repeating
    trying a LLC NULL packet
    sending fragmented packet
    still nothing, trying another packet
    I hit 'y' for yes
    and it just goes on.

    Oh the .ivs file does continue to get larger but I'm afraid it would take days to get enough packets from a system that has little or no activity.

    So I then tried aireplay-ng -9 eth1
    It finds all WEP encrypted AP's in my area but no answers.
    To me from what very little I know this is telling me I am not able to inject packets?
    Any help or constructive suggestions would be greatly appreciated. Thank you for your time to read this poorly written question.

  2. #2
    Administrator sickness's Avatar
    Join Date
    Jan 2010
    Location
    Behind the screen.
    Posts
    2,921

    Default Re: aireplay-ng problem

    The card works in Backtrack R2, you just have to search: http://www.backtrack-linux.org/forum...upgrading.html
    Back|track giving machine guns to monkeys since 2007 !

    Do not read the Wiki, most your questions will not be answered there !
    Do not take a look at the: Forum Rules !

  3. #3
    Good friend of the forums gunrunr's Avatar
    Join Date
    Jan 2010
    Location
    shining my spoon
    Posts
    265

    Default Re: aireplay-ng problem

    And since you arent creating packets to cap with a client connected to the station you might try using a arp replay attack instead. It tends to give about 250 ivs per second when it works.
    Wielder of the spoon of doom
    Summercon, Toorcon, Defcon, Bsides, Derbycon, Shmoocon oh my
    Come hang out with hackers on twitter @gunrunr556

  4. #4
    Just burned his ISO
    Join Date
    Apr 2011
    Location
    Las Vegas
    Posts
    5

    Default Re: aireplay-ng problem

    Quote Originally Posted by aaronramsdell View Post
    After confirming that I am receiving many AP's along with my test AP I then
    use airodump-ng --bssid xx:xx:xx:xx:xx:xx --channel 6 --ivs -w mytestssid eth1

    I start seeing beacons and data counting up, data counting up slowly.
    I then leave this open and open another terminal and use aireplay-ng -5 -b xx:xx:xx:xx:xx:xx eth1.

    I get this response
    No answer, repeating
    trying a LLC NULL packet
    sending fragmented packet
    still nothing, trying another packet
    I hit 'y' for yes
    and it just goes on.

    Oh the .ivs file does continue to get larger but I'm afraid it would take days to get enough packets from a system that has little or no activity.

    So I then tried aireplay-ng -9 eth1
    It finds all WEP encrypted AP's in my area but no answers.
    To me from what very little I know this is telling me I am not able to inject packets?
    Any help or constructive suggestions would be greatly appreciated. Thank you for your time to read this poorly written question.
    When you run the test it will tell you something like "Injection Working!" Also, for my laptop It uses my internal RTL chipset. I have had issues with my wlan0, but after putting it into mon0, Its a huge difference. It was the difference between something working completely and not working at all.

    As far as my aireplay commands, I almost never use -5, I never need to. I have always had success with aireplay-ng -1 0 -a (BSSID) -e (ESSID) mon0(or interface). After I get a success, then I start my aireplay -3 -b (BSSID) -h (Faked Mac - Optional) mon0.

    Going back to your packet injection, I have seen the same thing "no answer, etc." but if you test using aireplay-ng -9 (interface) It will tell you if injection is working.

Similar Threads

  1. Aireplay-ng Problem
    By mr_key in forum Beginners Forum
    Replies: 4
    Last Post: 03-07-2010, 07:07 PM
  2. Aireplay problem
    By blindnz in forum OLD Newbie Area
    Replies: 7
    Last Post: 02-22-2009, 02:37 PM
  3. aireplay-ng problem
    By imported_prophet in forum OLD Newbie Area
    Replies: 6
    Last Post: 01-06-2009, 04:25 AM
  4. Problem with Aireplay-ng
    By Darkcode in forum OLD Newbie Area
    Replies: 4
    Last Post: 08-13-2008, 07:45 PM
  5. problem .. aireplay-ng
    By TomRiddle in forum OLD BT3beta Bugs and Fixes
    Replies: 1
    Last Post: 06-29-2008, 07:32 AM

Posting Permissions

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