How to setup an Access Point via hostapd – Including using the TL-WN725N


I recently had to setup an Access Point using my TL-WN725N which allowed me to share my internet to multiple devices whilst my in-built WiFi on my laptop was connected to a WiFi Access Point with an internet connection. This was because only one device could be connected using the access code which I paid quite a lot of money for and thus I couldn’t connect my phone, or other devices.

In this tutorial, I will guide you through step by step on how to install the required software, and use a very helpful piece of software that does all the hard work for you.

Install the required software

Download and Install create_ap

create_ap is an excellent piece of software that manages hostapd and all the networking for you. It is run via command line and is very easy to use. You can read the README for it here on Its github page.

In order to install this, we are going to create a directory called “src” in the home directory. This is where we will download the code to and run the install command from.

NOTE: The install command places the file in /usr/bin or /usr/local/bin so it can be used from the command line without specifying its directory.

Start an AP

In order to start an Access Point (AP) we need to know what the device is called.

Run the following command;

We should see something like this;

NOTE: I removed my MAC Address and replaced it with numbers for privacy 🙂

I know wlan1 is going to be my Access Point adapter since I ran ifconfig before and after I plugged it in. All you need to know now is the other name of the device you want to share internet from.

To start an AP with wlan1 as the AP, and let’s say, wlan0 as the source adapter which is currently connected to a WiFi network with internet access, then run;

This should start up correctly and you should be able to find and connect to the WiFi AP. When you connect, you should be able to use the internet. You can find more examples by reading the README on the github page.

Using the TL-WN725N as an AP

If you followed everything above and it fails to start an AP, this is probably because you need to download a special version of hostapd for Ralink support. This is what I had to do in order to use the TL-WN725N USB adapter which uses the ralink drivers.

Before we start, let’s remove hostapd since we’re going to compile and install our own version;

Now we download hostapd to our src directory and extract it;

And finally, compile and install;

The last step will move the compiled hostapd binary to /usr/local/bin, add a startup script and create a configuration file in /etc/hostapd/hostapd.conf.

Now it is a good idea to reboot your device and then try and use the command above with the “–driver rtl871xdrv” paramter to start an AP. Hopefully it works!

An example would be;

How to install FFMPEG, Libx264, LibRTMP, LibAACPlus, LibVPX on the Raspberry Pi (Debian “Wheezy” ARMHF)

In the past I’ve had to been required to install FFMPEG for applications such as Serviio or a website like Clipbucket. It can be quite stressful since you could get dependency issues if you tried reading any other tutorials online, since the worst nightmare is if something breaks when you have compiled software using wrong dependencies. But this tutorial should ensure that it’ll work first time.

 UPDATE (12/10/2016): I’ve since updated this tutorial to add two new codecs for FFMPEG. I’ve also changed the FFMPEG repository to the official one rather than VideoLan. I’ve tested this complete tutorial for my Raspberry Pi 3 and it works fine.

Removing any existing dependencies

It’s vital to uninstall everything we’re going to be compiling/installing just in case there have been custom compilations of software that might be corrupted or broken. I’ve had a few errors in the past which resulted in “Illegal Instruction” when executing “ffmpeg” in the terminal.

Just copy and paste this into your terminal and hit enter. Type y and hit enter when necessary.

Downloading the Dependencies

Copy and Paste the commands below. When it asks, type and press Enter. This will download and install everything we need for later on.

Downloading & Compiling FFMPEG AND It’s Modules

Before we get started, we will be working inside a folder within the home directory. It is important not to remove this file in-case you want to uninstall anything later. Type the commands below in order and follow through.

Downloading & Compiling LibaacPlus

Again, type the below commands in order, and then move onto the next step.

Downloading & Compiling Libx264

 Downloading & Compiling LibVPX

NOTE: if you see the command output for “./configure” incorrectly identify the Pi as ArmV7 instead of ArmV6, try running the configure command again with the following parameter;

Downloading & Compiling LibRTMP

Now, before we move on, it’s important to run the command

This will update the system and make it aware of the new packages which have been installed.

Downloading & Compiling Libfaac

When you’re in the nana editor, you will need to go to line 126. Once you’re at that line, make the below code the same as in the file…

Once you’re finished, press CTRL + O to save, and then hit enter, then press CTRL + X to close the editor.

Then carry on…

It’s important to do a reboot just to make sure everything is being recognised and found.

Downloading & Compiling LibFDK-aac

Downloading & Compiling FFMPEG (Latest Version)

NOTE: This took my Raspberry Pi (Model B) around ~2 hours when overclocked to “Turbo” – 1GHz.

Finishing up

Now that FFMPEG has been compiled and installed successfully, we will need to reboot to make sure that everything is working. Type in;

When the Pi boots up, type in “ffmpeg” and you should see an output similar to that of what I get below;

And that’s it! You have now successfully installed FFMPEG on your Raspberry Pi! 🙂


The Raspberry Pi is a small credit-card sized computer. It’s very low powered and can be powered by a mini-usb cable and USB plug, such as a modern day phone charger. The Raspberry Pi (Model B) has a stock 700Mhz Armv6 processor and 512MB of RAM. The processor can be overclocked in the configuration to a maximum of 1Ghz (WARNING – Overclocking the Pi may void your warranty and break it).

When software utilises FFMPEG, you will see that it may bring the processor usage to 100% on the pi. This will cause the SoC to heat up rapidly unless you have a heatsink or some other form of cooling. At 100% CPU utilisation, the temperature without a heatsink can reach up to 80 Degrees Celsius!

Feel free to comment below and ask any questions!

How to run Boinc & BoincTUI on the Raspberry Pi

Before we start, I would like to take this time to explain what BOINC actually is.

What is BOINC?

BOINC is an open-source piece of software that allows users to volunteer their computers idle time to carry out scientific research. This in turn is called Grid-Computing. In other words, you can register to become part of a project which uses your computers’ idle time to search for new cures for diseases or help gain a better understanding of our galaxy. There are plenty of research projects available which you can find here.

Installing BOINC on the Raspberry Pi

In order to install BOINC on the Raspberry Pi, you will need to make sure that you have enough space on the SDCard. Other than that, you can go ahead and install it by typing in…

This will install BOINC and the GUI if you want to Remote Desktop (presuming its headless) into the Pi and check up on your projects instead of using the text interface.

Installing BOINCTUI on the Raspberry Pi

This was a little frustrating at first, however I managed to get help on the Raspberry Pi forums from a user named ghans.

Start off by navigating to the home directory by typing in cd ~/. Then type in the following to download the source code into the folder “boinctui” – presuming you have subversion installed. If not, then type in

Download source code –

After the source code has downloaded, cd into the directory by typing in “cd boinctui” – without the quotes.

Then follow, in order, the commands listed;

The compiling took me about 20 minutes give or take with my Pi over-clocked @ 1GHz.

NOTE: If you get any errors about missing libraries when running ./configure, you may need to run the following commands;

Once it’s finished, type in boinctui to load the Text-Based Interface and ta-da!. You can now manage your boinc-client with ease.