|
|||||||
| BackTrack 4 Working Hardware Post your Hardware Specs here. |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Thanks, That is what I am using. I finally have it working, but it is very slow.
|
|
|||
|
I would, but my computer is injecting packets painfully slow. I would not wish that on anyone. I will create one as soon as I can get it working faster.
Can you help me understand the different drivers used in BT Beta and BT Pre-Final for the iwl3945 driver? Backtrack 4 beta is fast, while Backtrack 4 Pre is extremely slow. |
|
||||
|
Quote:
More than likely it is probably the same one.
__________________
The very existence of flame-throwers proves that some time, somewhere, someone said to themselves, You know, I want to set those people over there on fire, but I'm just not close enough to get the job done. George Carlin |
|
|||
|
BackTrack 4 pre-final
Aireplay-ng 1.0 rc3 r1552 Kernal 2.6.29.4 Intel (R) PRO/WIRELESS 3945ABG/BG Networking Connection driver for linux, 1.2.26kds Backtrack 4 beta Aireplay-ng 1.0 rc2 r1385 Kernal 2.6.28.1 Intel (R) PRO/WIRELESS 3945ABG/BG Networking Connection driver for linux, 1.2.26k Never had a chance to see what the difference between the 1.2.26k and 1.2.26kds are. I did a lsmod and I think bt4 prefinal may be using a few extra modules (forgot to write them down, I will later maybe). I tried to revert back to Aireplay-ng 1.0 rc2 r1385 in BT4 Pre-Final but that had no effect. |
|
|||
|
Quote:
|
|
|||
|
ipw3945 works for me with some modification and using the ipwraw driver. Not sure if it is part of the issue but mine is (rev 02), not sure if other people having an issue are also rev 02, i posted a how to (in the wrong place - sorry!), in pre-final working hardware. look there is your having issues.
|
|
|||
|
Using Backtrack 4 Pre-Final.
Only mods: apt-get update apt-get upgrade Tested Linksys WUSB54G Ver4 Annoyances: TXpower won't go above 15db Pro's: Packet injection fast, works very efficiently Config I used for this device airmon-ng stop wlan0 ifconfig wlan0 down macchanger --mac 00:11:22:33:44:55 wla0 airmon-ng start wlan0 airodump-ng -c {channel num} --bssid {bssid of AP} -w {dumpfile name} wlan0 In a new term. aireplay-ng -3 -b {bssid of AP} wlan0 in a new term aireplay-ng -1 0 -a {bssid of AP} wlan0 The reason I ran in injection mode before doing a fake auth, is I find it the quickest way to do it. Just my preference. That works fine for me, packet injection rate is around 500pps. Not tried faster injection rates, thats fast enough for me ![]() Also tried the exact same commands as above with an Alfa AWUS036H and here are the results. Cons: Tx power won't go above 20dbM even though the equipment is 5 times more powerful than that. Packet injection is slow @ around 20pps However, if I substitute wlan0 for mon0, (including the macchanger command) then packet injection works @ 500pps no hassle. Would probably go faster, but no need. I'm not convinced though that the packet injection works properly, with specific reference to receiving ARP responses. It seems that I have to wait until a client generates an ARP for me, then things fly into action. Those are my experiences so far. /Jimbo |
![]() |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|