I'd suggest you reformat that post to use code boxes to make it a little bit more readable.
inel 3945abg can't inject?
BT4
# uname -a
Linux i-lomon 2.6.29.4 #1 SMP Thu Jun 18 10:57:32 EDT 2009 i686 GNU/Linux
# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11abg ESSID:"Jo9b"
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Tx-Power=13 dBm
Retry min limit:7 RTS thrff Fragment thr=2352 B
Encryption key
Power Management
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
mon0 IEEE 802.11abg Mode:Monitor Frequency:2.437 GHz Tx-Power=13 dBm
Retry min limit:7 RTS thr
Encryption key
Power Management
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
then,start:
# airmon-ng start wlan0 6
Found 5 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!
PID Name
4299 dhclient3
4359 dhclient3
5780 avahi-daemon
5783 avahi-daemon
32609 dhclient
Process with PID 4359 (dhclient3) is running on interface wlan0
Interface Chipset Driver
wlan0 Intel 3945ABG iwl3945 - [phy0]
(monitor mode enabled on mon0)
# aireplay-ng -1 0 -a 00:21:27:3D:B4:F6 -h 00:1C:BF5:3F:53 mon0
19:46:04 Waiting for beacon frame (BSSID: 00:21:27:3D:B4:F6) on channel 6
19:46:04 Sending Authentication Request (Open System) [ACK]
19:46:04 Authentication successful
19:46:04 Sending Association Request [ACK]
19:46:04 Association successful :-) (AID: 1)
# aireplay-ng -5 -b 00:21:27:3D:B4:F6 -h 00:1C:BF
19:46:52 Waiting for beacon frame (BSSID: 00:21:27:3D:B4:F6) on channel 6
19:46:52 Waiting for a data packet...
Read 427 packets...
Size: 68, FromDS: 1, ToDS: 0 (WEP)
BSSID = 00:21:27:3D:B4:F6
Dest. MAC = FF:FF:FF:FF:FF:FF
Source MAC = 00:21:27:3D:B4:F6
0x0000: 0842 0000 ffff ffff ffff 0021 273d b4f6 .B.........!'=..
0x0010: 0021 273d b4f6 3007 9dcf 0200 3e84 1622 .!'=..0.....>.."
0x0020: e68c 0aa1 2d7f dc5e 3c69 73e4 f784 861c ....-.^<is.....
0x0030: 6bdb 914a 2426 d6d0 f189 d672 3bde 9c0d k..J$&.....r;...
0x0040: 63cc 3b87 c.;.
Use this packet ? y
Saving chosen packet in replay_src-1203-194704.cap
19:47:08 Data packet found!
19:47:08 Sending fragmented packet
19:47:10 No answer, repeating...
19:47:10 Trying a LLC NULL packet
19:47:10 Sending fragmented packet
19:47:12 No answer, repeating...
19:47:12 Sending fragmented packet
19:47:13 No answer, repeating...
19:47:13 Trying a LLC NULL packet
19:47:13 Sending fragmented packet
19:47:15 No answer, repeating...
19:47:15 Sending fragmented packet
19:47:16 No answer, repeating...
19:47:16 Trying a LLC NULL packet
19:47:16 Sending fragmented packet
19:47:18 No answer, repeating...
19:47:18 Sending fragmented packet
19:47:19 No answer, repeating...
19:47:19 Trying a LLC NULL packet
19:47:19 Sending fragmented packet
19:47:21 No answer, repeating...
19:47:21 Sending fragmented packet
19:47:22 No answer, repeating...
19:47:22 Trying a LLC NULL packet
19:47:22 Sending fragmented packet
19:47:24 No answer, repeating...
19:47:24 Sending fragmented packet
19:47:25 No answer, repeating...
19:47:25 Still nothing, trying another packet...
signal strength is good.and try change router to test,but similar.
the always packets,can't get .xor file,so my 3945abg can't support inject? what's problem?
Thank you!
I'd suggest you reformat that post to use code boxes to make it a little bit more readable.
Capitalisation is important. It's the difference between "Helping your brother Jack off a horse" and "Helping your brother jack off a horse".
The Forum Rules, Forum FAQ and the BackTrack Wiki... learn them, love them, live them.
I know I'll sound like everyone else here, I promise, 3945 is supported, and does inject. The forum search function is a great feature
secure_IT has a great tut on this, you can also try:
hxxp://forums.remote-exploit.org/tutorials-guides/6567-how-enable-intel-pro-wireless-3945abg-card-backtrack.html
iwl3945
Note: This page is about the iwl3945 driver. For the older ipw3945/ipwraw driver, see ipw3945.
Intel PRO/Wireless 3945ABG, mac80211 driver
Iwl3945 is the new driver for the Intel PRO/Wireless 3945ABG wireless chipset. It includes new features like:
Managed and monitor mode support in one driver
Enhanced injection support
Multiple interfaces on one device - use the aircrack suite on a monitor interface while remaining associated on a managed interface
Full radiotap support, for both incoming and outgoing packets
No more binary regulatory daemon needed, regulatory enforcement is done by the firmware
The driver is based on the mac80211 stack, so the usual requirements apply (aircrack-ng 1.0-rc1, a recent version of libnl, a fairly new kernel, etc.)
Installing the driver
Starting with 2.6.24, the driver is included in the kernel. Injection requires 2.6.25 or later. The compat-wireless-old package must be installed and patched to get injection support on 2.6.25 and 2.6.26. For 2.6.27 and newer, no special patch is needed, follow the common instructions for mac80211.
*UPDATE* Apparently the new version of compat-wireless should *not* be patched and should work out of the box. more can be found here: iwlwifi drivers with injection * WORKING with 3945 & 4965 cards
Installing and patching compat-wireless
Install your kernel headers and sources, as well as all packages required for building kernel modules.
Download compat-wireless from here . For 2.6.26 and older, use compat-wireless-old, for newer versions (currently 2.6.27-rcX), use compat-wireless-2.6.
Untar the archive to your home directory. This will create a dated directory ~/compat-wireless-DATE, where DATE is the build date of the package.
Download the fragmentation patch , and apply it to the compat-wireless package. This is needed to make attacks -5 and -7 work.
Cd to the compat-wireless directory, and run “make” to build the package.
Install the package with “make install”, then load it with “make load”.
If you get errors during “make load”, reboot and all should work.
Using iwl3945 with aircrack-ng
Before using the card with aircrack-ng, you must create a monitor interface, using the command
airmon-ng start wlan0
where wlan0 is the interface name of the card. This will create a monitor interface called “mon0” (prefix changeable using the $MON_PREFIX environment variable, e.g. a $MON_PREFIX of “rtap” will result in an interface called “rtap0”). Next, run
airodump-ng -c <channel>,<channel> mon0
where <channel> is the channel the target AP is running on, while mon0 is the monitor interface you created in the first step. You must enter the channel twice, e.g. ”-c 3,3”, otherwise it will reset to channel 1. This is a bug in the driver, and a fix for it has been scheduled for inclusion into the kernel. After this, use “mon0” as the interface name for all monitoring/injection tasks.
sorry,i'm new man,can't post URL
my linux is 2.6.29.4
should i use ipw3945 instead of iwl3945?
then Installing and patching compat-wireless ?
Posting Permissions
