Search the Community
Showing results for tags 'tx power'.
Hi all, I'm a newbie to Hak5 Forums, so if this thread is in the wrong category, it would be great if the admins could move it to the correct category. Most of you are probably using 'BO' as the region for 'iw' on Linux. This allows the WiFi interface to operate at 30dBm (1 Watt) at max. However, if you're like me and have a device that is capable of transmitting over 1W (I have Alpha Network AWUS036NH - 2W), you might be interested in increasing the TX power beyond 30dBm. By default, selecting 'BO' as the region only allows the device to operate at a maximum of 30dBm. I tested this on my Raspberry Pi 3, Model B running Kali Linux (with the kali-linux-full metapackage). *** If you are lazy and don't want to follow these manual steps below, I made two bash scripts that will work on Kali Linux and Ubuntu : https://github.com/hiruna/wifi-txpower-unlocker Working directory: /root Steps: 1. Update and upgrade apt-get update apt-get upgrade 2. Install dependencies to compile apt-get install pkg-config libnl-3-dev libgcrypt11-dev libnl-genl-3-dev build-essential 3. Download the latest Central Regulatory Domain Agent (CRDA) and Wireless Regulatory Database I downloaded crda-3.18.tar.xz and wireless-regdb-2017.03.07.tar.xz wget https://www.kernel.org/pub/software/network/crda/crda-3.18.tar.xz wget https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2017.03.07.tar.xz 4. Unzip the downloaded files tar xvJf crda-3.18.tar.xz tar xvJf wireless-regdb-2017.03.07.tar.xz 5. Navigate into wireless-regdb-2017.03.07 cd wireless-regdb-2017.03.07 6. Open db.txt and locate the region BO section nano db.txt You will see something like this: country BO: DFS-JP (2402 - 2482 @ 40), (30) (5250 - 5330 @ 80), (30), DFS (5735 - 5835 @ 80), (30) The number in the second set of brackets (for each frequency) is the txpower. Since I'm using the 2.4Ghz and want a txpower of 2W (~33dBm), I changed the 20 to 33, and saved the file: country BO: DFS-JP (2402 - 2482 @ 40), (33) (5250 - 5330 @ 80), (30), DFS (5735 - 5835 @ 80), (30) I also noticed that region AU allows 36dBm for 2.4Ghz, so you could just continue without modifying the region BO: country AU: DFS-ETSI (2400 - 2483.5 @ 40), (36) (5150 - 5250 @ 80), (23), NO-OUTDOOR, AUTO-BW (5250 - 5350 @ 80), (20), NO-OUTDOOR, AUTO-BW, DFS (5470 - 5600 @ 80), (27), DFS (5650 - 5730 @ 80), (27), DFS (5730 - 5850 @ 80), (36) (57000 - 66000 @ 2160), (43), NO-OUTDOOR However, I checked with Kali Linux (without compiling and changing the regulatory.bin) and it showed that max txpower was only 20dBm: country AU: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 17), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW (5490 - 5710 @ 160), (N/A, 24), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 30), (N/A) So I'm assuming Kali Linux is using an old regulatory.bin and legislation in AU has changed. 7. Compile make 8. Backup up your old regulatory.bin file and move the new file into /lib/crda mv /lib/crda/regulatory.bin /lib/crda/regulatory.bin.old mv regulatory.bin /lib/crda As mentioned in https://wireless.wiki.kernel.org/en/developers/regulatory/crda and https://wireless.wiki.kernel.org/en/developers/regulatory/wireless-regdb, we need to include RSA public keys in crda-3.18/pubkeys. I noticed that there are already 2 .pem files in crda-3.18/pubkeys: sforshee.key.pub.pem linville.key.pub.pem 9. Copy root.key.pub.pem into crda-3.18/pubkeys. I also copied sforshee.key.pub.pem from wireless-regdb-2017.03.07 as it was newer: cp root.key.pub.pem ../crda-3.18/pubkeys/ cp sforshee.key.pub.pem ../crda-3.18/pubkeys/ I found that there are two other pubkeys located at /lib/crda : -rw-r--r-- 1 root root 451 Jan 18 12:58 firstname.lastname@example.org -rw-r--r-- 1 root root 451 Jan 18 12:58 linville.key.pub.pem -rw-r--r-- 1 root root 451 Jan 18 12:58 sforshee.key.pub.pem So I copied them too (wasn't too sure whether I needed to copy them): cp /lib/crda/pubkeys/benh\@debian.org.key.pub.pem ../crda-3.18/pubkeys/ cp /lib/crda/pubkeys/linville.key.pub.pem ../crda-3.18/pubkeys/ 10. Navigate into crda-3.18 and open the Makefile cd ../crda-3.18 nano Makefile In Kali Linux, crda is located at /lib/crda instead of /usr/bin/crda, so in the file change the 3rd line REG_BIN?=/usr/lib/crda/regulatory.bin to REG_BIN?=/lib/crda/regulatory.bin : REG_BIN?=/lib/crda/regulatory.bin 11. In the Makefile, find the line CFLAGS += -std=gnu99 -Wall -Werror -pedantic and remove the -Werror option (I couldn't compile without changing it as it treats warnings as errors): CFLAGS += -std=gnu99 -Wall -pedantic 12. Compile make clean make make install That's it! I rebooted my Raspberry Pi after compiling. reboot 13. Now let's change the region and set the txpower to 33dBm: ifconfig wlan1 down iw reg set BO iwconfig wlan1 txpower 33 ifconfig wlan1 up
Hello everyone, I apologize if I have missed a thread where this has been covered and appreciate your help and time ^^ I have this card and I could set the tx power on windows 7 and after installing windows 8.1 pro I cannot find this option anymore, help ? I think there is an option to set the tx power even higher, anyone know? Problem I have is when I use windows 7 in VMWare, for some reason there isn't any tx power option, maybe only when it's installed as host? Also I have other questions regarding finding wpa key, can I post it here?
What's up community, So I was going through the Wifi-Megaprimer series from Vivek / securitytube.net - good stuff. Anyways, there was a section on "Alfa Card kung-fu" which basically talked about changing tx power and things of that sort by altering the Country Code for the regulatory domain. What I'm wondering, is if there is any way to change the "disabled" frequencies to be "enabled". I'm sure it's based off the Country Code as well so i'm thinking there is no way to do this??? That's what brings me to asking my fellow nerds. *My screen shots are to big and i don't really have time to mess with em at the moment* OS: Kali Linux 1.0.7 NIC: Dual Band Alfa Card 802.11 a/b/g/n - AWUS051NH - Ralink chipset - monitor works, tested with Airodump - Injection works, tested with aireplay-ng -9 -b xx:xx:xx:xx:xx:xx mon0 --ignore-negative-one -9 = test -b = BSSID --ignore-negative-one = !#$%@#$@##$@#%$!#$@%@#$@ Tools: Kali Alfa card Wireshark - for verification Aircrack suite test AP ifconfig wlan* down #replace the wildcard with your adapters number iw reg set BO # BO is the country code, the codes tell your NIC what rules to follow based on the countries FCC equivalent. Originally mine was set to GB - Great Britain i believe. iwconfig wlan* txpower 30 # in dBm (Decibel mW ), my card was at 27 dBm (.5W) by default - this changed it 30 dBm (1W) - I'm pretty sure the FCC wont like this to much, testing purposes though :-> ifconfig wlan* up # blah blah blah anyways... after unplugging the Alfa from the comp and going to lunch, it reset itself back to default plug a interface in, turn it on if you need to and run the command: iw list #shows details about the wireless cards, you can scroll down and see the freq/channel. That list is what the question revolves around. side notes: *yes, i have Googled and researched for half of today to no avail* * doing this has made my card temporarily act a bit funny when running Airodump-ng - random stops, slow channel scanning, no displayed results* *the card seems to change back after unplugging it* - not to sure if there is a comit or anything that I missed but this is just testing anyways so.* * You may or may not have to take the interface down to make the change, a few times while trying this i didn't do "ifconfig wlan down" but "iw list" showed the changes take effect while the card was up the whole time* Thanks in advance guys/girls, take care
Hi guys i was trying to change the txpower on an external alfa wireless card (to get a better transmittion) via ssh on the pineapple but was not able to do so, has anybody tried to change it? the commands i run are iw reg set BO < this command runs fine > iwconfig wlan1 txpower 30 < here i get the following error > Error for wireless request "Set Tx Power" (8B26) : SET failed on device wlan1 ; invalid argument. maybe i should have a look on the openwrt forum but figured id ask on here also..