How to use your Raspberry Pi as a wireless access point

How to use your Raspberry Pi as a wireless access point

The Raspberry Pi can do a lot, especially now that the new Raspberry Pi comes with wireless capabilities already on board. It can take the place of a ton of different (and more expensive) devices – including a router! If you turn your Raspberry Pi into a wireless access point, you can make it act as a router. It’s not the most powerful thing in the world, but it does work, and the project is a lot of fun.

How to use your Raspberry Pi as a wireless access point

We’re going to get into the command line a bit here, but this project isn’t really all that difficult. All we’re really doing is using Raspbian and installing a couple packages that give the Pi the ability to do router-like things like assign IP addresses to devices that connect to it.

Step 1: Install and update Raspbian

Check out our complete guide to installing Raspbian for the details on this one. Then plug everything in and hop into the terminal and check for updates and ugrades:

sudo apt-get update
sudo apt-get upgrade

If you get an upgrade, It’s a good idea to reboot with sudo reboot.

Step 2: Install hostapd and dnsmasq

These are the two programs we’re going to use to make your Raspberry Pi into a wireless access point. To get them, just type these lines into the terminal:

sudo apt-get install hostapd
sudo apt-get install dnsmasq

Both times, you’ll have to hit y to continue. hostapd is the package that lets us create a wireless hotspot using a Raspberry Pi, and dnsmasq is an easy-to-use DHCP and DNS server.

We’re going to edit the programs’ configuration files in a moment, so let’s turn the programs off
before we start tinkering:

sudo systemctl stop hostapd
sudo systemctl stop dnsmasq

Step 3: Configure a static IP for the wlan0 interface

For our purposes here, I’m assuming that we’re using the standard home network IP addresses, like 192.168.###.###. Given that assumption, let’s assign the IP address to the wlan0
interface by editing the dhcpcd configuration file. Start editing with this command:

sudo nano /etc/dhcpcd.conf

Now that you’re in the file, add the following lines at the end:

interface wlan0
static ip_address=
denyinterfaces eth0
denyinterfaces wlan0

(The last two lines are needed in order to make our bridge work –- but more on that in
Step 8.)

After that, press Ctrl+X, then Y, then Enter to save the file and exit the editor.

Step 4: Configure the DHCP server (dnsmasq)

We’re going to use dnsmasq as our DHCP server. The idea of a DHCP server is to
dynamically distribute network configuration parameters, such as IP addresses, for
interfaces and services.

dnsmasq’s default configuration file contains a lot of unnecessary information, so
it’s easier for us to start from scratch. Let’s rename the default configuration file and
write a new one:

sudo mv /etc/dnsmasq.conf /etc/dnsmasq.conf.orig
sudo nano /etc/dnsmasq.conf

You’ll be editing a new file now, and with the old one renamed, this is the config file that dnsmasq will use. Type these lines into your new configuration file:


The lines we added mean that we’re going to provide IP addresses between and for the wlan0 interface.

Step 5: Configure the access point host software (hostapd)

Another config file! This time, we’re messing with the hostapd config file. Open ‘er up:

sudo nano /etc/hostapd/hostapd.conf

This should create a brand new file. Type in this:


Note that where I have “NETWORK” and “PASSWORD,” you should come up with your own names. This is how you’ll join the Pi’s network from other devices.

We still have to show the system the location of the configuration file:

sudo nano /etc/default/hostapd

In this file, track down the line that says #DAEMON_CONF=”” – delete that # and put the path to our config file in the quotes, so that it looks like this:


The # keeps the line from being read as code, so you’re basically bringing this line to life here while giving it the right path to our config file.

Step 6: Set up traffic forwarding

The idea here is that when you connect to your Pi, it will forward the traffic over your Ethernet cable. So we’re going to have wlan0 forward via Ethernet cable to your modem. This involves editing yet another config file:

sudo nano /etc/sysctl.conf

Now find this line:


…and delete the “#” – leaving the rest, so it just reads:


Step 7: Add a new iptables rule

Next, we’re going to add IP masquerading for outbound traffic on eth0 using iptables:

sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

…and save the new iptables rule:

sudo sh -c "iptables-save > /etc/iptables.ipv4.nat"

To load the rule on boot, we need to edit the file /etc/rc.local and add the following
line just above the line exit 0:

iptables-restore < /etc/iptables.ipv4.nat

Step 8: Enable internet connection

Now the Raspberry Pi is acting as an access point to which other devices can connect. However, those devices can’t use the Pi to access the internet just yet. To make the possible, we need to build a bridge that will pass all traffic between the wlan0 and eth0 interfaces.

To build the bridge, let’s install one more package:

sudo apt-get install bridge-utils

We’re ready to add a new bridge (called br0):

sudo brctl addbr br0

Next, we’ll connect the eth0 interface to our bridge:

sudo brctl addif br0 eth0

Finally, let’s edit the interfaces file:

sudo nano /etc/network/interfaces

…and add the following lines at the end of the file:

auto br0
iface br0 inet manual
bridge_ports eth0 wlan0

Step 9: Reboot

Now that we’re ready, let’s reboot with sudo reboot.

Now your Pi should be working as a wireless access point. Try it out by hopping on another device and looking for the network name you used back in step 5.


This piece has been updated for Raspbian Stretch and is based on the instructions created by GitHub user SurferTim.

53 Comments on "How to use your Raspberry Pi as a wireless access point"

  1. flasterofreality | July 9, 2017 at 3:51 pm | Reply

    This is one of the best tutorials I have seen for the Pi3 with using onboard Wi-Fi! Thanks for including the /etc/rc.local config for iptables that often gets overlooked.

  2. Thanks for this, it works better than several other tutorials I’ve tried.

    But, what I’m really looking for is not a hotspot with its own IP range, but an extension of my existing Ethernet network with DHCP done on the main router. So that all devices can see each other. Do you have any ideas about how to accomplish that? There is a guide on the Raspberry Pi website, which uses bridge, but it doesn’t work.

    • Try to remove all configurations of dnsmasq and dhcp. Uninstall dnsmasq.
      Then remove the firewall settings, as it starts masquerading, that is, make the RPi and other LAN on different IP ranges with NAT. You don’t want that.

      Set the RPi to get IP address from dhcp or static IP from the other networks network address. I would try dhcp first.

      Good luck!

      The rest should be enough to make it work after reboot.

  3. Can anyone help me, I have it all working but when i try to connect it says that there is no internet connection and it will not fully connect it will load forever. Do I have to port-forward the Raspberry Pi on my router or is it something i have to fix in the code?

    • What is the network address of the network you connect to eth0? If it is (that is the IP address prefix is 192.168.0.) you should change the prefixes on your configuration on the RPi to something else like 192.168.42 or something. The number 42 could be anything between 1 and 255.

      So, we need to see what router you uses.

      Try the command ‘ip route’ on the RPi.

  4. So I followed SurferTims tutorial and pretty much ended up doing what you’ve got here except with different IPs — do you know how to add a captive portal to this AP so it points to an Apache web server on the Raspberry Pi?

  5. Really good, worked well, with VNC its a simple cut and paste

  6. Hello and thank you for the tutorial. It’s the only one working since updating to Stretch… 🙂

    Now that I’ve replicated the tutorial, I’d like to implement a slightly different version of it. I’d like to use the Raspberry Pi 3 as an access point AND as a client simultaneously. This is for a little project I’m working on (building a weather station). This should be possible with the Wi-Fi chipset built into the Raspi. There is no need for the clients that access the Raspi AP to have internet connectivity, so there’s no need for forwarding traffic (only the Raspi needs internet connectivity). I’m rather new to networking on Linux, so I don’t bring much experience to the table. Unfortunately, there is no other way than this to realize the project. Can this be done by simply altering some of the above steps? What would be the right way of doing so? If not, could anyone give me some pointers to it?

    I have found some tutorials for doing so, but all of them work with /etc/network/interfaces. Unfortunately, editing anything in this file breaks access to wireless connectivity… (“no wireless interface found”)

    Hopefully someone can help me. Thanks in advance!

    Kind regards,

  7. Could you please say why it is losing connection in 30 sec after start? (I can’t see SSID in Wi-Fi list and no connection between the RPi and my phone.)

  8. Unfortunately I did exactly as described (twice) and I can’t connect to the Raspberry Pi.

  9. I tried use it on another Raspberry Pi – the same problem.

  10. Great tutorial. But some things.

    Don’t use or, as they are usually used in default configuration on home routers. Use a random number x in range 2-255 in 192.168.x.0/24 for your network. Then the risk of trouble with routing will be less. Even if you have MASQUERADE on.

    The firewall rules should also be set up, as NAT is not a secure firewall.

    I recommend using ufw there, with a new enough version also do support being a router.

  11. Thanks for this guide!

    All other solutions I tried sometimes Wi-Fi is not available any more and i have to reboot the RPi.

    Is there a way for this setup to check if it’s up and running and (automatic) take steps needed to get it up and running again?

  12. It would be helpful to see what the resulting ifconfig and route output looks like with some explanation, so that we could confirm that we did everything right and could make adjustments for our own specific situation with a deeper understanding. Thanks.

  13. Million thanks to you! I’ve been trying to setup wireless Pi AP for two days now, and this tutorial finally did it! What other tutorials around the web didn’t have was the bridge part, and they left you with access point sure but without any connection to the net.

  14. Is it possible to use this approach to use an Android device as a remote desktop of the RPi (using VNC) when there is no network (i.e., in the field)? Thanks.

  15. when I used the command:
    sudo brctl addif br0 eth0

    It shown an error: Can’t add wlan0 to bridge br0: Operation not supported

    Please help to fix this error!

  16. I found out that Pi is not connecting to router AP (as client). I tried connecting manually using GUI, but not working.

  17. Thanks for the guide.

    I think that, in case you are not interested on Step 8 (i.e., you just want to access your Raspberry Pi through SSH or VNC even in the absence of Wi-Fi network), you also have to avoid the two lines with denyinterfaces in /etc/dhcpcd.conf (Step 3). At least this is how it works for me. Please confirm.

  18. Many thanks for this AP, I’ve been working on it for about two months.

    My application is remote temperature monitoring of bee hives.

    My set-up is AP–Pi-Zero-W–USB/Ethernet–Home Router(Wi-Fi disabled)–Debian PC along with Wi-Fi devices Win7Lap Top and Galaxy/Android
    AP static IP, range …11 to …30.

    The Android/Firefox goes online through the AP just fine.

    Android/Fing and Win7/Control Panel list Gateway as, i.e., the home router, not the Pi AP at

    Win7/Firefox not happy.

    On Android/Termius/BotSync/etc attempts to reach the Pi at are thwarted.

    What might I try to log on to the Pi? From Android for Terminal/rsync, etc.

  19. Thanks for the how-to on this. I’m looking to turn my Pi into a VPN, and got to this tutorial from the VPN post.

    After going through these instructions, I’m not seeing a broadcast of my Pi’s network. When I reboot, the Wi-Fi connects automatically to the last hotspot, but I’ve tried turning that off as well with no luck.

    Am I missing anything? Thanks for any insight.

  20. Hi, I use SSH on Ethernet port. It seems that br0 already exists. How can I create a wireless access point without touching Ethernet port?

  21. Ernesto Galdamez | January 4, 2018 at 6:53 pm | Reply

    I tried another tutorial to make this work, but this solved my issue with no internet connection. The other tutorial forgot about the bridge connection with eth0. Thanks in advance for so helpful information! I’m trying to setup my RPi3 as a captive portal and needed this.

  22. Thanks for this how-to. I got it up and working. I’ve had it working for about a few weeks now, but for some reason the Wi-Fi seems to drop of disconnect after 30-45 minutes. If I’m connected via Wi-Fi, it drops. Logging into it via keyboard/monitor, I can’t go anywhere. It’s like the entire network just dies.

    Any suggestions on how to re-cycle the connections or adapters?

  23. Peter Barsznica | January 9, 2018 at 4:43 am | Reply

    ALL worked first go! Thanks heaps!

  24. Is this running well?

  25. Well… I tried twice and nothing is working. 🙁 Should the Wi-Fi magically appear when rebooting?

  26. Same here ^

    Does the Wi-Fi adapter need to remain in managed mode?

  27. Bridge isn’t working. When I put in command “sudo brctl addif br0 eth0” it says “interface eth0 does not exist.” Can anyone help?

  28. Does you Pi need to be connected to a router over Ethernet?

  29. Hi,

    First of all, thank you so much for this tutorial!! I tried several others and this is the only one that truly and easily worked!
    I’m having a little problem though. Other devices (like my smart TV for instance) can actually connect to my Raspberry, but when I use OpenVPN to connect my Raspberry to a NordVPN server, these devices don’t take advantage of the VPN. I thought that when the Raspberry is using OpenVPN, any device that connects to it would connect to the VPN as well but it doesn’t seem to be as simple as that and I missing something here. Do you have any advice or tip to help me finish my little project? Thank you!

  30. Thanks for the tutorial, it works perfectly!

    One question though: I have a local server running on port 9123. How could I bridge all traffic except for this port?

  31. If you don’t see the Wi-Fi hostpot check that hostapd service is up and running. That’s the one exposing the SSID.

    For those wanting a all-in-one hotspot you can try this one:

  32. It works however I’m still getting an IP from the main router range and not between

  33. Well done!

    Thank you for helping me get this working. Tried multiple others and was glad to find one that works with Stretch!

    If I could suggest a mod, it would be calling out the aspects that drive bridge mode vs. acting as a standalone AP/router.

    Ideally, I’m going for an AP that can also route traffic through the eth0 (if connected) but function independently if no Internet is available. After disabling the bridge/denyinterface parts, I’ve got the AP functioning in standalone mode, and the Pi can see the Internet, but Wi-Fi connected clients cannot. Getting closer!

  34. I followed the tutorial and I can see the broadcast SSID, but when I am trying to connect to the Pi I can’t obtain an IP address.

  35. Adding a bridge after you configured DNS, DHCP and NAT masquerading seems to be incorrect. These are two distinct configurations, after all.

    If you bridge eth0 and wlan0 together, these essentially become parts of the same subnet with Pi being completely transparent. In this case the DNS/DHCP functionality should be coming from the Ethernet, and the whole dnsmasq and iptables business is not needed.

    If, instead, you configure the Pi as a router, it becomes a proper host inbetween two separate subnets (one for eth0 and one for wlan0). In this case you do need dnsmasq and the iptables routing, however you should not bridge eth0 and wlan0.

    • Hi Konstantin,

      I am having the same problem as Jeremy (see below). I actually figured out that there is something wrong when obtaining the IP address – it gets an IP address from the main router and not from the “raspberry-router”.

      You pointed that out in your comment. My question now: How do I have to change the settings so that the Raspberry actually becomes a router?

      Thanks in advance,

  36. Hi,

    Everything works fine apart from one thing. I have no internet on Raspberry Pi, so I can’t even run sudo apt-get update. I did this to run a VPN. Can you tell me what happened?

  37. Unfortunately, it doesn’t work for me. I have started from a fresh installation of Raspbian. When I join the Wi-Fi network, my device is given an IP address from the router behind the RPi3. When I manually configure the IP address within the range of the RPi3 DHCP server, it doesn’t work at all. Any advice?

  38. Unable to get this to work on my 3B+. When it tries to boot it hangs up in the bluetooth area. If I wait a while it will finally boot but is locked up.

  39. Thanks for the tutorial. It “kind” of works. 🙂
    I’m using usb0 instead of eth0 (USB tethering). My issue is actually that the local Pi doesn’t get internet access. Everything that connects to it gets bridged, but the AP itself is denied access to the usb0 network.

  40. Hi,

    I had problems recently setting up the bridge on a B+ Pi where it stopped the Pi from booting with a “Kernel Oops” error.. Others have seen the same and raised this bug report ( Based on the comments in there I was able to update the firmware to resolve the issue (sudo raspi-config). This only seems to affect the B+ and not earlier models.

    It’s working great now!


  41. Choong Kar Yan | April 14, 2018 at 3:25 pm | Reply

    Hi! Unfortunately, it doesn’t work on my RPi3. I can’t find the SSID broadcast name and don’t have any idea what is going on. Hope to get some help and guide, thank you!

  42. This worked for AP but it screwed up my SSH, xrdp and Pi-hole. Any ideas on how to fix that?

  43. Hi!

    I would like to use this or if there is some other approach already in place for a headless setup so that you can connect to the RPi with your phone and then set up your Wi-Fi connection. Instead of preconfiguring the WPA config through an SD card reader, similar to setting up ESPEasy.

    Any suggestions?

  44. This tutorial skips the step of running “iptables-restore < /etc/iptables.ipv4.nat" manually.

    Every tutorial I've tried with Raspberry stretch has an issue with this step, so if you don't do it manually, it won't work and you'll have no error messages.

    This is the error (Raspberry Pi 3):

    "iptables-restore v1.6.0: iptables-restore: unable to initialize table 'nat'

    Error occurred at line: 2"

    Every similar process I've tried results in this error and I haven't been able to get past it.

    I don't know why some people have success and I haven't multiple times.

  45. The latest version of hostapd does not play well with wpa_supplicant on Stretch. The simplest way to to fix this is to disable wpa_supplicant on the wireless interfaces you want to run hostapd on. You can do this by adding the following line to to the relevant WLAN interface stanzas in /etc/dhcpcd.conf.

    nohook wpa_supplicant


    interface wlan0
    nohook wpa_supplicant
    static ip_address=

    If you think about it it makes sense. Wpa_supplicant is a service to authenticate clients to access points. Hostapd is a service that runs the wireless interface as an access point that will receive authentication request from clients. Running both hostapd and wpa_supplicant on an interface does not make any sense and only worked by accident in the past.

  46. Succeeded in getting this to work on a Pi 3B+. However in order to do so I found Stretch Lite doesn’t name eth0 but uses a longer string of letters and numbers. “ifconfig” revealed this in place of eth0.

    I kept Step 7’s “sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE” but strangely in Step 8 I had to substitute eth0 with the new name shown by “ifconfig”.

  47. David Hansen | May 23, 2018 at 6:18 am | Reply

    I added the nohook wpa_supplicant line that was suggested by Roger James and that fixed my lack of internet on the Pi 3.

  48. Did not work for me.

    I’ve tried it many times and with more than one Raspberry. And in any case the access point appears to my devices, I’m sure I did the correct procedures.

Leave a comment

Your email address will not be published.