Tim's Technology Journey Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====Easy Raspberry Pi WiFi Bridge====
[[https://pimylifeup.com/raspberry-pi-wifi-bridge/|Easy Raspberry Pi WiFi Bridge]]
===Summary===
by Gus  May 08, 2017  Updated Jun 01, 2019  Beginner, Network
A Raspberry Pi WiFi bridge is one of the best ways of providing internet access to a device that only supports an Ethernet connection.

Raspberry Pi WiFi Bridge
In this tutorial, we will show you how to setup a WiFi bridge, and how to setup dnsmasq correctly to allow any device to connect through your Pi without issues.

You will need to keep in mind that you will not see speeds as good as what you would with a direct connection to your router. As there is some overhead with the connection having to run through the Raspberry Pi.

Remember to do this tutorial you will need either a WiFi dongle or a Raspberry Pi 3 with the inbuilt WiFi module.

===Equipment List===
Below are all the bits and pieces that I used for this Raspberry Pi WiFI bridge tutorial, you will need A Wireless internet connection to be able to complete this tutorial.

Recommended
  * Raspberry Pi 2 or 3
  * Micro SD Card
  * Wifi dongle (The Pi 3 has WiFi inbuilt)
  * Ethernet Connection

===Setting up the WiFi Bridge===
To setup the Raspberry Pi Wifi bridge we will be utilizing the dnsmasq package, this package handles most of the grunt work for this tutorial.

Dnsmasq is a package that acts as both a local DHCP server and a local DNS server. We utilize this package so that we can assign IP addresses and process DNS requests through the Raspberry Pi itself and act like a router.

One of the bonuses to utilizing dnsmasq is that it is very easy to configure while being somewhat lightweight in comparison to the isc-dhcp-server and bind9 packages.

Remember for this tutorial you will need to have an active WiFi router to connect to and an ethernet device you intend on bridging the Wi-Fi connection to.
  - Before we get started with installing and setting up our packages, we will first run an update on the Raspberry Pi by entering the following two commands into the terminal.<code>sudo apt-get update
sudo apt-get upgrade</code>
  - With that done we can now install the one and only package we will be utilizing, run the following command to install dnsmasq.<code>sudo apt-get install dnsmasq</code>
  - Before we get too far ahead of ourselves, we should setup the wlan0 connection that we plan on using. If you have already setup your wireless connection then you can skip ahead to step 5.\\ Otherwise open up the wpa_supplicant file by running the following command:<code>sudo nano /etc/wpa_supplicant/wpa_supplicant.conf</code>
  - Within this file add the following, making sure you replace the ssid with the name of the network you want to connect to and replace the psk value with the password for that network.<code>network={
        ssid="networkname"
        psk="networkpassword"
}</code>
  - With the wireless network now setup to correctly connect we can proceed with setting up our eth0 interface. This will basically force it to use a static IP address, not setting this up can cause several issues.\\ To do this we need to modify the dhcpcd.conf fileby running the following command:<code>sudo nano /etc/dhcpcd.conf</code>\\ Important Note: If you’re on Raspbian stretch then wlan0 and eth0 may need to be changed if predictable network names is turned on. Use the ifconfig command to see the new names, they’re likely quite long and will contain the MAC address.\\ Make sure you update these for all the commands in this tutorial.
  - Within this file we need to add the following lines, make sure you replace eth0 with the correct interface of your ethernet.<code>interface eth0
static ip_address=192.168.220.1/24
static routers=192.168.220.0</code>\\ Now we can save and quit out of the file by pressing Ctrl+X then pressing Y and then Enter.
  - With our changes made to dhcpcd configuration we should now restart the service by running the following command:<code>sudo service dhcpcd restart</code>
  - Before we get started with modifying dnsmasq’s configuration we will first make a backup of the original configuration by running the following command.<code>sudo mv /etc/dnsmasq.conf /etc/dnsmasq.conf.orig</code>
  - With the original configuration now backed up and moved out of the way we can now move on and create our new configuration file by typing the command below into the terminal.<code>sudo nano /etc/dnsmasq.conf</code>
  - Now that we have our new file created we want to add the lines below, these lines basically tell the dnsmasq package how to handle DNS and DHCP traffic.<code>interface=eth0       # Use interface eth0  
listen-address=192.168.220.1   # Specify the address to listen on  
bind-interfaces      # Bind to the interface
server=8.8.8.8       # Use Google DNS  
domain-needed        # Don't forward short names  
bogus-priv           # Drop the non-routed address spaces.  
dhcp-range=192.168.220.50,192.168.220.150,12h # IP range and lease time</code>\\ Now we can save and quit out of the file by pressing Ctrl+X then pressing Y and then Enter.\\ 
  - We now need to configure the Raspberry Pi’s firewall so that it will forward all traffic from our eth0 connection over to our wlan0 connection. Before we do this we must first enable ipv4p IP Forwarding through the sysctl.conf configuration file, so let’s begin editing it with the following command:<code>sudo nano /etc/sysctl.con</code> note: the filename ends in .conf
  - Within this file you need to find the following line, and remove the # from the beginning of it.\\ Find:<code>#net.ipv4.ip_forward=1</code>\\ Replace with:<code>net.ipv4.ip_forward=1</code>\\ Now we can save and quit out of the file by pressing Ctrl+X then pressing Y and then Enter.
  - Now since we don’t want to have to wait until the next reboot before the configuration is loaded in, we can run the following command to enable it immediately.<code>sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward"</code>
  - Now that IPv4 Forwarding is enabled we can reconfigure our firewall so that traffic is forwarded from our eth0 interface over to our wlan0 connection. Basically this means that anyone connecting to the ethernet will be able to utilize our wlan0 internet connection.\\ Run the following commands to add our new rules to the iptable:<code>sudo iptables -t nat -A POSTROUTING -o wlan0 -j MASQUERADE  
sudo iptables -A FORWARD -i wlan0 -o eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT  
sudo iptables -A FORWARD -i eth0 -o wlan0 -j ACCEPT</code>\\ Note: If you get errors when entering the above lines simply reboot the Pi using sudo reboot.
  - Of course iptables are flushed on every boot of the Raspberry Pi so we will need to save our new rules somewhere so they are loaded back in on every boot.\\ To save our new set of rules run the following command.<code>sudo sh -c "iptables-save > /etc/iptables.ipv4.nat"</code>
  - Now with our new rules safely saved somewhere we need to make this file be loaded back in on every reboot. The most simple way to handle this is to modify the rc.local file.\\ Run the following command to begin editing the file.<code>sudo nano /etc/rc.local</code>
  - Now we are in this file, we need to add the line below. Make sure this line appears above exit 0. This line basically reads the settings out of our iptables.ipv4.nat file and loads them into the iptables.\\ Find:<code>exit 0</code>\\ Add Above:<code>iptables-restore < /etc/iptables.ipv4.nat</code>\\ Now we can save and quit out of the file by pressing Ctrl+X then pressing Y and then Enter.
  - Finally all we need to do is start our dnsmasq service. To do this, all you need to do is run the following command:<code>sudo service dnsmasq start</code>
  - Now you should finally have a fully operational Raspberry Pi WiFi Bridge, you can ensure this is working by plugging any device into its Ethernet port, the bridge should provide an internet connection to the device you plugged it into.\\ To ensure everything will run smoothly it’s best to try rebooting now. This will ensure that everything will successfully re-enable when the Raspberry Pi is started back up. Run the following command to reboot the Raspberry Pi:<code>sudo reboot</code>
Tim's Technology Journey Wiki

User Tools

Site Tools

Page Tools
