The Wi-Fi in our house is pretty decent, but my room is very far off from the study room where the router is located. Which means that my streaming box loses the connection a couple of times throughout the hour, which is really not optimal when you’re streaming movies. After watching the spinning icon for the umpteenth time, I decided to extend the range of the signal with a Wi-Fi access point.

I had a spare Raspberry Pi, some time to kill, and an Ethernet cable to my room. Should be pretty easy, right? Most of the tutorials online, however, only taught how to make a Wi-Fi repeater with a Raspberry Pi. Now, for the unaware, a Wi-Fi repeater is terrible because you’re essentially cutting the bandwidth in half and causing more congestion for the network in your area. An AP (access point), on the other hand, is significantly better because the communication between your Raspberry Pi and your router happens through the Ethernet jack, leaving the radio on the Raspberry Pi free for all client devices to communicate.

So let’s get started! This guide assumes you have the latest Raspbian Stretch Lite flashed on a SD card with balenaEtcher inside the Raspberry Pi.

Steps 1-3 are optional. Skip ahead if you have a monitor, keyboard, and mouse attached to the Raspberry Pi. If you want to work remotely using your laptop, you must follow steps 1-3.

  1. Connect your SD card to your computer. If your operating system asks if you want to format your card, do NOT select format. If you’ve accidentally formatted the card, burn the Raspbian Stretch image again with balenaEtcher.
  2. Create an empty file called ssh or ssh.txt inside the /boot partition of the USB. This asks the Pi to enable SSH on first boot.
  3. Eject the card and plug it into the Pi.
  4. Make sure the Pi is connected to an Ethernet network.
  5. Start up the Pi and connect to it using SSH. If you don’t know the Pi’s IP address, download Fing on your phone (Android/iOS) and do a scan on your network. If that doesn’t show anything, try running arp -a on any terminal. If that doesn’t work, use nmap. As a last resort (and potentially the first place you might check if your router is decent), connect to the router’s administration page and check the DHCP leases. My router is capable of this but it never showed any devices in the list except the one I was connecting from, so the feature was absolutely useless for me.
  6. The default username and password is pi and raspberry. Let’s first change the password!
  7. Change the password using passwd.
  8. sudo apt update to fetch latest update manifests.
  9. sudo apt upgrade -y to update the packages.
  10. sudo rpi-update to update firmware.
  11. sudo reboot to reboot and apply the new firmware.
  12. sudo apt install hostapd to get Wi-Fi hosting tools.
  13. sudo systemctl stop hostapd to stop hostapd. We don’t need it for now and we need it disabled to edit the configuration.
  14. sudo apt install bridge-utils to install bridging utilities.
  15. sudo brctl addbr br0 to create a bridge interface. This is what the Wi-Fi clients will use while connecting.
  16. sudo nano /etc/hostapd/hostapd.conf to create configuration for hostapd:
# driver=nl80211
hw_mode=g # Available options are a for 5GHz, and b and g for 2.4GHz


You must comment out driver or else it will fail. Once finished, type Ctrl-O, and then Enter to save. Type Ctrl-X to exit.

  1. sudo nano /etc/default/hostapd to apply new configuration. Find the line that says


And uncomment it. Edit like so:



Save and exit.

  1. We need to bridge the two connections. Run sudo brctl addif br0 eth0.

  2. Add these lines with sudo nano /etc/network/interfaces:

allow-hotplug wlan0
iface wlan0 inet manual

auto br0
iface br0 inet dhcp
bridge_ports eth0 wlan0


  1. We need to prevent the Pi from assigning eth0 and wlan0 to new network interfaces. Add the following lines with sudo nano /etc/dhcpcd.conf:
denyinterfaces wlan0
denyinterfaces eth0


  1. Enable hostapd
sudo systemctl unmask hostapd
sudo systemctl enable hostapd
sudo systemctl start hostapd
  1. Finally, run sudo reboot to start your new AP! When rebooting, there might be an error: Failed to start dhcpcd on all interfaces. This is normal and should be ignored.

Once that’s done, place your Pi where the Wi-Fi connection is weak and connect to the Pi to enjoy your new wireless access point!


I had a bit of a performance issue with the Raspberry Pi Wi-Fi access point, and wondered why it was considerably slower than the main Wi-Fi access point.

To test this, I set up an iperf3 server and then ran tests between my laptop (a ThinkPad X250) and the server, going through the Pi-AP or directly. The results were disappointing. The direct connection gave me 100Mbps of throughput - very well, seeing as this is Cat.5 cable, but the Pi-AP gave about 20Mbps. What the hell?

I tried using a different, crappy Chinese AP, and it gave me a consistent throughput of 70Mbps. About what I was expecting, give or take. I have two theories as to what is going on. Theory number one is that the Pi is underpowered, and therefore suffers from Ethernet/Wi-Fi lag. Theory number two is that the packets first go to the router (or default gateway) for inspection, come back to the Pi and then go to the intended recipient. Then the cycle repeats as the packets make their way back to the client.

So this project will work in a cinch, but performance will definitely suffer and you’ll be better off with an actual access point in the long run.