TP-Link WN725N v2 WIFI on the Raspberry PI

TP-Link WN725N v2 on Raspberry Pi at N speeds (150 Mbps).

So I managed to get the wireless nano-dongle to work on one of my Raspberry Pi’s. It’s a TP-Link WN725N version 2. It has N capabilities, and it wasn’t easy making sure I got N speeds either, more on that later.


To get the drivers into the kernel, I used the script downloadable in this forum post:

You might have to edit the script, basically change the part …/phpBB3/… to …/forums/…
Just run the script and reboot.

N-speeds and connecting it to your network 

Then we want to make sure we get the N-protocol up and running. The key to this lies in the security settings of the wireless, not the Raspberry Pi.
If you run

iwconfig wlan0

the output should look something like:

wlan0     IEEE 802.11bgn  ESSID:”SSID”  Nickname:”<WIFI@REALTEK>”
          Mode:Managed  Frequency:2.437 GHz  
          Bit Rate:72.2 Mb/s   Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:****-****-
          Security mode:open
          Power Management:off
          Link Quality=100/100  Signal level=100/100  

and some other things.
Here you can see I get all three, b+g+n. If it says “bg” you’re doing it wrong, given that you have a N-capable router…

To get it working, you have to only have the AES (CCMP) security ONLY, i.e. NOT TKIP, TKIP is the older security protocol, and gives you only G-speeds, i.e. 54 Mbps. So to fix this, make sure the wireless is setup with WPA(2) AES security. NOTE: this dongle only has one (1) antenna, that’s why the N-speed is 150 Mbps, you need an adapter with 2 antennae to get 300 Mbps, but then you probably need a powered USB-hub too.

Then in /etc/network/interfaces you can have (given that you have DHCP and not static IPs):

auto lo

# ethernet
iface lo inet loopback
iface eth0 inet dhcp

# The WLAN network interface
allow-hotplug wlan0
iface wlan0 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
iface wlan0 inet dhcp

and then for the important part, in /etc/wpa_supplicant/wpa_supplicant.conf

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev


and then it should all be dandy. Some guides tell you to go with something else for “proto” and “pairwise” and don’t include “group”, these are the TKIP guides, giving G-speeds.

Note: If only get, ~72 Mbps, you should try to activate channel bonding, i.e. get the channel bandwidth of the wireless network (router, ap, etc) of 40 MHz, as opposed to 20 MHz (so it clumps two 20 MHz channels together). However, this can degrade the signal in crowded areas, that’s why mine says 72 Mbps.

Reboot and enjoy!

Usefull links:
TKIP vs. AES and setup :
WPA2-PSK setup:

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.


Raspberry Pi baby monitor – Hardware, part 1

Raspberry Pi baby monitor In this first of a multi-part post I will show my build of a Raspberry Pi…

Sync FitBit with Google Fit

Finally: sync FitBit and Google Fit at high time resolution! I have been trying to figure out a way to…

Monitor dependent setup in i3wm

Multiple configurations for different monitor setups in i3wm General Figure 1:¬†Anyone that recognize this image might find this "guide" useful!…

Installing IRAM GILDAS on Ubuntu

    Figure: Screenshot of GILDAS MAPPIN in action viewing an imported FITS spectral cube.Fore information on IRAM GILDAS, see…

%d bloggers like this: