User Tools

Site Tools


wpa_migration_mode

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
wpa_migration_mode [2010/08/11 17:45] lmeinerswpa_migration_mode [2010/08/29 19:43] – Fixed channel/frequency graph link mister_x
Line 92: Line 92:
           Retry  long limit:  RTS thr:off   Fragment thr:off           Retry  long limit:  RTS thr:off   Fragment thr:off
           Power Management:off           Power Management:off
-          
 </code>  </code> 
  
 In the response above, you can see that mon0 is in monitor mode, on the 2.447GHz frequency which is channel 8 and the Access Point shows the MAC address of your wireless card. Please note that only the madwifi-ng drivers show the MAC address of your wireless card, the other drivers do not do this. So everything is good. It is important to confirm all this information prior to proceeding, otherwise the following steps will not work properly.  In the response above, you can see that mon0 is in monitor mode, on the 2.447GHz frequency which is channel 8 and the Access Point shows the MAC address of your wireless card. Please note that only the madwifi-ng drivers show the MAC address of your wireless card, the other drivers do not do this. So everything is good. It is important to confirm all this information prior to proceeding, otherwise the following steps will not work properly. 
  
-To match the frequency to the channel, check out: http://www.rflinx.com/help/calculations/#2.4ghz_wifi_channels then select the “Wifi Channel Selection and Channel Overlap” tab. This will give you the frequency for each channel.+To match the frequency to the channel, check out: http://www.cisco.com/en/US/docs/wireless/technology/channel/deployment/guide/Channel.html#wp134132 . This will give you the frequency for each channel.
  
 ==== Step 2 - Start airodump-ng to capture the IVs ==== ==== Step 2 - Start airodump-ng to capture the IVs ====
Line 172: Line 171:
  
 It will start listening for ARP requests and when it hears one, aireplay-ng will bitflip it and immediately start to inject it.  It will start listening for ARP requests and when it hears one, aireplay-ng will bitflip it and immediately start to inject it. 
-<code>+
 Here is what the screen looks like when ARP requests are being injected:  Here is what the screen looks like when ARP requests are being injected: 
 +<code>
 12:17:52  Waiting for beacon frame (BSSID: 00:26:0B:2A:BA:40) on channel 8 12:17:52  Waiting for beacon frame (BSSID: 00:26:0B:2A:BA:40) on channel 8
 Saving ARP requests in replay_arp-0811-121752.cap Saving ARP requests in replay_arp-0811-121752.cap
wpa_migration_mode.txt · Last modified: 2018/03/11 20:19 by mister_x