| ||||||||||||||||||||
| ||||||||||||||||||||
Search Irongeek.com:
Help Irongeek.com pay for bandwidth and research equipment: |
You must first retrieve the PCI memory address of the module by
lspci -v and maybe activate the module by
setpci (see example below).
DISCLAIMER: Use the write function only if you know what you are doing! There is the chance to
brick your module.The authors arent responsible for any damage caused by using this program.
Transmitting on illegal frequencies may violate state laws. Obey the local regulations!
Execute the commands below from a root account.
Retrieve the modules PCI memory address with lspci:
# lspci -v
0b:00.0 Ethernet controller: Atheros Communications, Inc. AR5211 802.11ab NIC
(rev 01)
The above card has its memory mapped at 0x6c000000.
If no madwifi driver is running or the module isnt recognized by the
driver anymore, e.g. due to wrong PCI id values (check your syslog),
you must manually enable the PCI device with setpci. The argument to "-s" comes
from the output above:
setpci -s 0b:00.0 command=0x41f cache_line_size=0x10
Retrieve some information of the module:
# ./ath_info 0x6c000000
Set the regulatory domain to 0. You need to confirm to write with y (-f turns this off).
Check http://madwifi.org/wiki/UserDocs/CountryCode for more information on
regdomains and country codes:
# ./ath_info -w 0x6c000000 regdomain 0
The write function is currently not tested with 5210 devices.
Use at your own risk, entering a false device address will have really
nasty results!
An invalid magic in the EEPROM will cause ath_info to fail.
15 most recent posts on Irongeek.com:
|
If you would like to republish one of the articles from this site on your
webpage or print journal please contact IronGeek.
Copyright 2020, IronGeek
Louisville / Kentuckiana Information Security Enthusiast