Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| docs:guide-user:network:wifi:relay_configuration [2022/08/16 20:19] – [Setup with LuCI Web Interface] Refresh with 21.02 LuCI Create Bridge interface - correct formatting error bill888 | docs:guide-user:network:wifi:relay_configuration [2024/06/22 06:26] – Final editorial pass richb-hanover | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| - | <WRAP center round important 80%> | + | This article describes how to make an OpenWrt router into a Wi-Fi repeater/ |
| - | If supported by both devices, consider using [[docs: | + | It makes a Wi-Fi connection to the "main router" |
| + | and acts as an AP (access point) for local devices with another radio. | ||
| + | The extender then relies on the '' | ||
| - | Using relayd as instructed in this article | + | For the sake of simplicity, |
| - | The most common problem | + | This configuration |
| + | where the main router | ||
| + | or does not support preferred [[docs: | ||
| + | or [[docs: | ||
| + | You may also wish to consider using an alternate [[: | ||
| - | Instead of relayd it should be possible to use **kmod-trelay**, | + | There is a Youtube video that shows substantially |
| - | </ | + | https://www.youtube.com/watch? |
| - | In this article you will see how to configure your device to become | + | The image below shows the normal configuration. |
| + | The "main router" | ||
| + | and its LAN port (192.168.1.1/ | ||
| + | The Wi-Fi extender is on the left. | ||
| + | It makes a wireless connection (labeled "W-LAN (Client)" | ||
| + | The Wi-Fi extender's other radio acts as an access point for local devices. | ||
| - | In some cases, the wireless drivers used in OpenWrt do not support "Layer 2" bridging in client mode with a specific " | + | \\ {{ docs: |
| - | When other options don't work or are too complex to implement, | + | Other notes on the configuration: |
| - | For the sake of simplicity, I'll call the device we are working | + | Even though all end devices on the Wi-Fi extender will get a DHCP address from the main router's LAN subnet, |
| + | The rest of this article uses 192.168.2.1 as the "Wi-Fi extender | ||
| - | \\ {{ docs:guide-user: | + | Since both ethernet ports and Access Point Wi-Fi network are on the same **LAN** interface, all clients connecting to the Ethernet ports and to the Access Point Wi-Fi network of the Wi-Fi extender device will be routed |
| - | This image shows an example setup. | + | The **LAN** interface |
| - | Since both ethernet ports and Access Point Wi-Fi network | + | You may use the same Wi-Fi network |
| + | settings | ||
| + | This allows wireless devices connected | ||
| + | Alternatively, | ||
| + | |||
| + | This procedure has been tested with OpenWrt 23.05.3 | ||
| - | The **LAN** interface subnet will be used only as a " | ||
| - | ===== Using relayd | + | ===== Setup with LuCI Web GUI ===== |
| - | ==== Required packages ==== | + | |
| - | **relayd** package is of course needed, and **luci-proto-relay** is optional for the LuCI Web Interface. | + | |
| - | ==== Setup with LuCI Web Interface ==== | + | ==== Configure LAN Interface ==== |
| - | Updated with screenshots from 21.02. \\ | + | The **LAN** interface of the Wi-Fi extender must be set in a different subnet than the main router. |
| - | \\ | + | |
| - | === LAN Interface === | + | * Remove any wired connections between your Wi-Fi extender and your main router. |
| - | As shown in the image above, the **LAN** | + | * Connect a computer with Ethernet to a LAN port on the Wi-Fi extender and log into LuCI web UI at 192.168.1.1 (default address) |
| + | * (Optional) Update | ||
| + | * On **System -> Backup/ | ||
| + | * Go to **Network -> Interfaces**, | ||
| + | * Set **LAN protocol** to **static address**, click **Change protocol** | ||
| + | * Assign an IP address using the "Wi-Fi extender subnet" | ||
| + | * Click **Save and Apply**. | ||
| - | Begin by configuring and enabling the normal Wi-Fi network and configure it as you want it.\\ | + | \\ {{media:docs:howto:relay_lan_changeip.jpg?400|}} \\ |
| - | If you are making a simple Wi-Fi repeater (a device that extends the same Wi-Fi network' | + | |
| - | But you can also choose to have a different name/ | + | |
| - | Setting up a Wi-Fi network at this stage is not necessary if you want a "Wi-Fi bridge", | + | |
| - | /*** old LEDE17 image | + | |
| - | \\ {{ :docs:guide-user:wifirepeater_interfaces_lan.png |}} \\ | + | |
| - | ***/ | + | |
| - | * Set **LAN protocol** as **static address** (default setting) | + | ---- |
| - | * Assign an IP address in a **different** subnet (e.g. 192.168.2.1). Click Save. | + | |
| - | * Disable DHCP for the **LAN** interface (as it does prevent **relayd** from working). | + | |
| - | * < | + | |
| - | * Click Save and Apply. | + | |
| - | \\ {{media: | + | * Reconnect to router at its new IP address (eg. 192.168.2.1) |
| - | ---- | + | * From **Network -> Interfaces**, |
| + | * Click the **DHCP Server** tab and disable DHCP, IPv6 RA-Service, and DHCP-v6 Service. To do this: | ||
| + | * On the **General Settings** tab, check the " | ||
| + | * On the **IPv6 Settings** tab, choose " | ||
| + | * See images below | ||
| + | * Click **Save**. | ||
| + | * Click **Save and Apply**. | ||
| + | * Finally, set your PC's Ethernet port to use a static IP in the Wi-Fi extender subnet | ||
| + | (e.g., 192.168.2.10) and default gateway (e.g., 192.168.2.1), | ||
| + | then connect again to the Wi-Fi extender via Ethernet. | ||
| + | |||
| \\ {{media: | \\ {{media: | ||
| ---- | ---- | ||
| \\ {{media: | \\ {{media: | ||
| - | ---- | + | ==== Configure |
| - | Set your PC's ethernet or Wi-Fi settings at static IP 192.168.2.10 and default gateway 192.168.2.1, | + | |
| - | \\ | + | |
| - | \\ | + | |
| - | \\ | + | |
| - | ---- | + | To configure the Wi-Fi connection to the main router. |
| + | * Keep your PC connected to the Wi-Fi extender via Ethernet. Remove any other physical connections. | ||
| + | * Navigate to the **Network | ||
| + | * Choose a radio to connect to the main router. Typically this should be a b/g/n radio, since they have longer range than 5GHz radios | ||
| + | * Click on **Scan** button for that radio. | ||
| - | === Wi-Fi === | + | \\ {{media: |
| - | We will now set up the client Wi-Fi network, the configuration needed to connect to another | + | |
| - | Navigate to the wireless networks page, and click on **Scan** button for the desired radio.\\ | + | * From the list of SSIDs found in the scan, choose |
| - | /*** old LEDE17 image | + | \\ {{media: |
| - | \\ {{ : | + | |
| - | ***/ | + | |
| - | \\ {{media: | + | |
| - | \\ | + | |
| - | \\ | + | |
| - | Choose the Wi-Fi network you want to connect to from the page and click "Join Network" | + | |
| - | \\ {{media: | + | |
| - | \\ | + | |
| - | \\ | + | |
| ---- | ---- | ||
| - | /*** | + | |
| - | \\ {{ :docs:guide-user: | + | * Set the "Name of new network" |
| - | ***/ | + | * Enter any Wi-Fi credentials such as WPA passphrase |
| + | * Select **lan** firewall zone. | ||
| + | * Click **Save**. | ||
| + | * Click **Save & Apply**. | ||
| - | Enter the Wi-Fi password, leave the "name of new network" | ||
| \\ {{media: | \\ {{media: | ||
| - | \\ | ||
| - | \\ | ||
| ---- | ---- | ||
| - | /*** old LEDE17 image | ||
| - | \\ {{ : | ||
| - | ***/ | ||
| - | You will land in the client Wi-Fi settings page. Edit as required.\\ | + | You will see the client Wi-Fi settings page (image below). Edit as required. |
| - | The most important settings are on the **Operating Frequency** line.\\ | + | The most important settings are on the **Operating Frequency** line. |
| - | Set the **Mode** to **Legacy** if you are connecting to a Wi-Fi g network, or **N** if you are connecting to a Wi-Fi n (and so on).\\ | + | |
| - | Set the **Width** to the same value that you set on the Wi-Fi you are connecting to (to avoid bottlenecking | + | * Set the **Mode** to **Legacy** if you are connecting to a Wi-Fi g network, or **N** if you are connecting to a Wi-Fi n (and so on).\\ |
| - | \\ | + | |
| - | \\ | + | * Keep the same Wi-Fi channel number. The extender must match the main router. |
| + | | ||
| + | | ||
| \\ {{media: | \\ {{media: | ||
| - | Click Save when finished. \\ | + | ==== Remove redundant WAN interface and firewall zones ==== |
| - | Click Save & Apply. \\ | + | |
| - | \\ | + | Although it's optional, it is recommended to delete the redundant WAN interfaces and firewall zones. |
| + | |||
| + | * Go to **Network -> Interfaces** (image below) | ||
| + | * Delete both '' | ||
| + | * Go to **Network > Firewall** (image below) | ||
| + | * Delete the '' | ||
| + | * Click **Save & Apply** | ||
| + | **Note:** These actions will also automatically remove any redundant firewall traffic and port forwarding rules. | ||
| + | \\ {{media: | ||
| - | ---- | + | \\ {{media: |
| + | ==== Add static IP on wwan ==== | ||
| + | |||
| + | It is recommended to assign a static IP address to newly created wwan interface. | ||
| + | This should be in the same subnet as the main router' | ||
| + | You can then manage the router using this static IP address. | ||
| + | This static IP address will also be used later when creating the Relay interface. | ||
| - | === Repeater Interface === | + | * Go to **Network -> Interfaces** |
| - | Go in the **Interfaces** | + | |
| - | Click on **Add New Interface**.\\ | + | |
| - | /*** old LEDE17 image | + | \\ {{media:docs:howto:relay_wwan_static_1.jpg?800|}} \\ |
| - | \\ {{ :docs:guide-user:wifirepeater_newinterface.png |}} \\ | + | |
| - | ***/ | + | |
| - | \\ {{media: | + | |
| - | ---- | + | |
| - | \\ | + | |
| - | \\ | + | |
| - | Enter a name and select | + | |
| - | (You may need to reboot your device before the **Relay bridge** option appears.) \\ | + | |
| - | Click 'Create Interface' | + | |
| - | \\ {{media: | + | |
| - | ---- | + | |
| - | \\ | + | |
| - | \\ | + | |
| - | Enter the IP address | + | |
| - | Select both **lan** | + | |
| - | \\ {{media: | + | |
| - | Click Save, \\ | + | |
| - | Click Save & Apply. | + | |
| - | \\ | + | \\ {{media: |
| - | \\ | + | |
| + | * On the **Advanced Settings** tab (image below) | ||
| + | * Set **Use custom DNS Servers** to the IP address of the main router (e.g., 192.168.1.1). | ||
| + | * Press **Save** | ||
| + | * Press **Save & Apply** | ||
| + | \\ {{media: | ||
| + | ==== Test Connection ==== | ||
| - | ---- | + | At this point, the Wi-Fi extender should be wirelessly connected to the main router. |
| - | old LEDE17 image | + | To verify the the connection: |
| - | \\ {{ :docs:guide-user:wifirepeater_relaybridge1.png |}} \\ | + | * Go to **Network |
| + | * Perform a ping test by clicking the "IPv4 Ping" button. | ||
| + | * A few moments later, you should see ping results if the main router is connected to the internet. | ||
| + | * | ||
| + | \\ {{media:docs:howto:relay_network_test.jpg?500|}} \\ | ||
| + | ==== Install relayd package ==== | ||
| + | * Go to **System -> Software**. | ||
| + | * Click **Update List** button. If the Wi-Fi extender is connected to the main router, and that is connected to the internet, a few moments later, the results of the update appears. | ||
| + | * Enter **luci-proto-relay** into the Filter box (image below), and click **Install**. | ||
| + | * When that completes, reboot the router from **System -> Reboot** (image below). | ||
| + | \\ {{media: | ||
| - | This "Local IPv4 address" | + | \\ {{media: |
| - | ---- | + | |
| - | ---- | + | ==== Create Relay Interface ==== |
| - | < | + | |
| - | /*** old LEDE17 image. Redundant. | + | Add the '' |
| - | \\ {{ :docs:guide-user: | + | * Go to **Network |
| - | ***/ | + | * Click on **Add New Interface** (image below) |
| + | \\ {{media: | ||
| + | * In the **Add new interface** window (image below) | ||
| + | * Enter a name (" | ||
| + | * Select **Relay bridge** protocol as shown below. (Reboot your device if the **Relay bridge** option fails to appears.) | ||
| + | * Click **Create Interface** | ||
| - | ---- | + | \\ {{media: |
| - | ---- | + | * In **Network |
| + | * Enter the IP address assigned to the '' | ||
| + | * Select both **lan** and **wwan** in the **Relay between networks** list. | ||
| + | * Click **Save**. | ||
| + | * Click **Save & Apply**. | ||
| + | * After you have completed above steps, reboot the router. | ||
| - | After you have done this, it might be necessary to reboot the Wi-Fi extender. | + | \\ {{media: |
| - | \\ {{ :docs:guide-user: | + | ==== Enable the AP ==== |
| + | Enable and configure the Wi-Fi extender to be an access point for local devices. | ||
| - | This is the final result. Note how the client network | + | * Go to **Network -> Wireless** |
| + | * Click **Edit** button for any item with **Mode: Master**. (Don't edit your Client connection to the main router.) | ||
| + | * In the Interface Configuration section, configure SSID, security and other parameters of your Wi-Fi extender so it can act like an access point. | ||
| + | * If you are configuring the same radio that also serves as the client | ||
| + | * Click **Save** | ||
| + | * **Enable** the wireless network. | ||
| + | * You might edit/enable other radios (for example, enabling both the b/g/n and n/ | ||
| + | * Click **Save & Apply**. | ||
| - | === Firewall | + | ==== You're Done - More Testing ==== |
| - | :!: The following part of the configuration | + | After configuring |
| + | and connect to the newly-configured Wi-Fi. | ||
| + | Your computer | ||
| + | The Wi-Fi extender can be managed through its static | ||
| - | old LEDE17 image | + | The **Status -> Overview** window (image below) shows the final result. |
| - | \\ {{ : | + | '' |
| - | Under the **Network** tab, click on the **Firewall** tab. Under **Zones**, change | + | '' |
| + | The client Wi-Fi has a ? in the **Host** column instead of a IP address | ||
| + | because its '' | ||
| - | ---- | + | \\ {{media:docs:howto: |
| - | :!: if you are doing this with a device that has a single radio, both Wi-Fi networks will stay on the same channel, and total bandwidth will be halved as the same radio is used for 2 different Wi-Fi networks. | + | |
| - | ==== Setup with CLI ==== | + | ===== Setup with CLI ===== |
| Before doing any actual configuration, | Before doing any actual configuration, | ||
| Line 288: | Line 330: | ||
| You will likely want to set up your device' | You will likely want to set up your device' | ||
| - | ==== Accessing the OpenWrt device | + | ===== Troubleshooting ===== |
| - | If you find the OpenWrt device | + | ==== Accessing the Extender |
| + | If you find the Wi-Fi extender | ||
| (The alternative is tedious: It is possible to access the OpenWrt box via its '' | (The alternative is tedious: It is possible to access the OpenWrt box via its '' | ||
| + | |||
| + | ==== Check Firewall zones ==== | ||
| + | |||
| + | :!: The following part of the configuration should not be necessary (already default options or changed automatically), | ||
| + | |||
| + | \\ {{media: | ||
| + | \\ | ||
| + | ---- | ||
| + | \\ {{media: | ||
| ==== Adding IPv6 support ==== | ==== Adding IPv6 support ==== | ||
| Line 309: | Line 361: | ||
| We suppose that you created a '' | We suppose that you created a '' | ||
| - | That's it. Restart '' | + | That's it. Restart '' |
| ==== Known Issues ==== | ==== Known Issues ==== | ||
| Line 317: | Line 369: | ||
| - DHCP issue caused by Access Point. [[https:// | - DHCP issue caused by Access Point. [[https:// | ||
| - Extremely poor upstream transfer speeds with some MT762x devices. [[https:// | - Extremely poor upstream transfer speeds with some MT762x devices. [[https:// | ||
| - | - Need additional | + | - [[https:// |
| + | - [[https:// | ||
| + | - Additional | ||
| + | - Connect a computer using ethernet cable to LAN port of the Wifi bridge. | ||
| + | - Configure a static IP address on the computer. eg. if the Wifi bridge uses LAN IP address of 192.168.2.1 in above example, use static IP address: 192.168.2.10. | ||
| + | - Access LuCI at 192.168.2.1 for above example. | ||
| + | - [[https:// | ||
| + | - Alternative detailed Relayd setup instructions can also be found in section 9.10 of the [[https:// | ||
| + | - IPv6 on macOS 10.15+ does not work with a ULA prefix set on LAN [[https:// | ||
| - | ===== Using NAT ===== | + | ==== Using NAT ==== |
| + | |||
| + | **<color # | ||
| + | \\ | ||
| + | \\ | ||
| This method basically puts a second Wi-Fi router in cascade on the first one; i.e. usually this means that the extender' | This method basically puts a second Wi-Fi router in cascade on the first one; i.e. usually this means that the extender' | ||