User Tools

Site Tools


ath5k

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
ath5k [2008/11/10 18:55] – Remove an addressed FIXME and minor update. netrolller3dath5k [2009/01/06 23:53] – Update for newer kernels. netrolller3d
Line 3: Line 3:
 Ath5k is a new, completely FOSS driver for Atheros cards. Wireless-N-enabled Atheros chipsets should use [[ath9k]] instead. Ath5k is a new, completely FOSS driver for Atheros cards. Wireless-N-enabled Atheros chipsets should use [[ath9k]] instead.
 Unlike madwifi-ng, this driver is based on the new [[mac80211]] stack, meaning that it requires aircrack-ng v1.0-rc1 or newer. Unlike madwifi-ng, this driver is based on the new [[mac80211]] stack, meaning that it requires aircrack-ng v1.0-rc1 or newer.
 +
  
 ===== Aircrack-ng support ===== ===== Aircrack-ng support =====
Line 10: Line 11:
 [[http://patches.aircrack-ng.org/ath5k-injection-2.6.27-rc2.patch]] [[http://patches.aircrack-ng.org/ath5k-injection-2.6.27-rc2.patch]]
 It is recommended that you also apply the mac80211 fragmentation patch for your kernel version, to enable the fragmentation attack. It is recommended that you also apply the mac80211 fragmentation patch for your kernel version, to enable the fragmentation attack.
 +For the released 2.6.27 and 2.6.28 kernels, the mac80211 patch suffices, no extra patch is needed.
 +
 +If you have a kernel older than 2.6.26, it's recommended that you install the latest compat-wireless-old package, and apply the 2.6.27 mac80211 fragmentation patch on the package itself. No ath5k-specific patch is needed for either flavor of compat-wireless.
  
-If you have a kernel older than 2.6.26it's recommended that you install the latest compat-wireless-2.6-old packageand apply the above patch (as well as the mac80211 fragmentation patch) on the package itself.+Note that in the latest wireless-testing & linux-2.6 kernelsas well as in compat-wireless-2.6 (but not in compat-wireless-old)there is a bug that prevents the fragmentation attack from working properly when no managed interface is brought up on the same PHY as the monitor interface. As a workaround, bring up wlan0 after creating mon0 with airmon-ng.
  
ath5k.txt · Last modified: 2017/01/09 21:36 by mister_x