User Tools

Site Tools


broadcom

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
Next revisionBoth sides next revision
broadcom [2008/12/28 14:35] – Added definition of supported devices. darkaudaxbroadcom [2009/08/14 19:05] – use dokuwiki internal link mister_x
Line 1: Line 1:
 ======= Broadcom bcm43xx ======= ======= Broadcom bcm43xx =======
  
-As of 2.6.17, a driver for the Broadcom bcm43xx wireless chipset has been included in the kernel. Older kernels can sometimes be made to work, check out resources available [[http://bcm43xx.berlios.de|here]] While this driver natively supports monitor mode, it requires patching before packet injection can be done. After testing aireplay-ng with the patches, please contribute to the [[http://tinyshell.be/aircrackng/forum/index.php?topic=281.0|forum thread]] by reporting any successes or failures there.+As of 2.6.17, a driver for the Broadcom bcm43xx wireless chipset has been included in the kernel. Older kernels can sometimes be made to work, check out resources available [[http://bcm43xx.berlios.de|here]] While this driver natively supports monitor mode, it requires patching before packet injection can be done. After testing aireplay-ng with the patches, please contribute to the [[http://forum.aircrack-ng.org/index.php?topic=281.0|forum thread]] by reporting any successes or failures there.
  
 **Note: As of 2.6.24, this driver is considered deprecated, and you might be better off using the new [[b43]] driver instead. (B43 supports the fragmentation attack, and it's much more stable than bcm43xx.)** **Note: As of 2.6.24, this driver is considered deprecated, and you might be better off using the new [[b43]] driver instead. (B43 supports the fragmentation attack, and it's much more stable than bcm43xx.)**
Line 22: Line 22:
     * See http://www.latinsud.com/bcm/     * See http://www.latinsud.com/bcm/
  
-Also see this [[http://tinyshell.be/aircrackng/forum/index.php?topic=2845.msg18262#msg18262|thread]] for more information.+Also see this [[http://forum.aircrack-ng.org/index.php?topic=2845.msg18262#msg18262|thread]] for more information.
  
 Use this patch instead of the one below. Use this patch instead of the one below.
Line 45: Line 45:
  
 Forum thread:  Forum thread: 
-[[http://tinyshell.be/aircrackng/forum/index.php?topic=2045.0|The complete how to of making bcm43xx injection work]]+[[http://forum.aircrack-ng.org/index.php?topic=2045.0|The complete how to of making bcm43xx injection work]]
  
 Forum thread:  Forum thread: 
-[[http://tinyshell.be/aircrackng/forum/index.php?topic=2845.0|How I got the bcm43xx packet injection working in ubuntu 7.10]]+[[http://forum.aircrack-ng.org/index.php?topic=2845.0|How I got the bcm43xx packet injection working in ubuntu 7.10]]
  
-This forum thread may also provide some useful information: [[http://tinyshell.be/aircrackng/forum/index.php?topic=281|Broadcom bcm43xx Injection]]+This forum thread may also provide some useful information: [[http://forum.aircrack-ng.org/index.php?topic=281|Broadcom bcm43xx Injection]]
  
  
Line 76: Line 76:
 It will give you the fully qualified file name.  Do "ls -l <fully qualified file name>" and confirm it has the date/time of when you compiled and installed the new module.  If it does not match, then you are not running the patched module.  This would, of course, need to be fixed. It will give you the fully qualified file name.  Do "ls -l <fully qualified file name>" and confirm it has the date/time of when you compiled and installed the new module.  If it does not match, then you are not running the patched module.  This would, of course, need to be fixed.
  
-This thread has a number of potential fixes to problems you may encounter: [[http://tinyshell.be/aircrackng/forum/index.php?topic=281|Broadcom bcm43xx Injection]]+This thread has a number of potential fixes to problems you may encounter: [[http://forum.aircrack-ng.org/index.php?topic=281|Broadcom bcm43xx Injection]]
  
  
Line 87: Line 87:
   * Error message: "ioctl(SIOCGIFINDEX) failed: No such device"   * Error message: "ioctl(SIOCGIFINDEX) failed: No such device"
  
-Then [[http://aircrack-ng.org/doku.php?id=faq#why_do_i_get_ioctl_siocgifindex_failedno_such_device|See this FAQ entry]].+Then [[faq#why_do_i_get_ioctl_siocgifindex_failedno_such_device|See this FAQ entry]].
  
  
  
  
broadcom.txt · Last modified: 2017/01/09 21:27 by mister_x