Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
docs:guide-user:network:wifi:relay_configuration [2021/11/03 16:47] – [Wi-Fi extender / repeater / bridge configuration] trendydocs:guide-user:network:wifi:relay_configuration [2024/06/22 06:26] – Final editorial pass richb-hanover
Line 1: Line 1:
-====== Wi-Fi extender repeater / bridge configuration ====== +====== Wireless Repeater/Extender with Relayd ====== 
-<WRAP center round important 80%> +This article describes how to make an OpenWrt router into a Wi-Fi repeater/extender/bridge. 
-If supported by both devices, consider using [[docs:guide-user:network:wifi:atheroswds|WDS]], Layer 2 GRE tunnels ("gretap")or [[docs:guide-user:network:wifi:mesh:start|mesh networking]].+It makes a Wi-Fi connection to the "main routerwith one of its radios, 
 +and acts as an AP (access point) for local devices with another radio.  
 +The extender then relies on the ''relayd'' package to bridge between the two connections.
  
-Using relayd as instructed in this article isn't guaranteed to work.+For the sake of simplicity, this article will use the term "Wi-Fi extender" from now on.
  
-The most common problem is that the client router cannot pass the DHCP message between the main router and the client connected to the client routerCurrently it seems to be the hardware/SOC limitation (related to MAC cloning?)+This configuration is useful where you do not control the main router
 +where the main router does not run OpenWrt, 
 +or does not support preferred [[docs:guide-user:network:wifi:atheroswds|Wireless Repeater/Extender with WDS]] 
 +or [[docs:guide-user:network:wifi:mesh:80211s|802.11s Mesh Networking]]. 
 +You may also wish to consider using an alternate [[:docs:guide-user:network:wifi:connect_client_wifi|simple wireless client]] where bridged network is not required.
  
-Instead of relayd it should be possible to use **kmod-trelay**, the only information about using it can be seen in [[https://github.com/openwrt/openwrt/commit/c3bba7f8c61ee98265bcffef8ee86e22aa89bbe9|its source code]], if you used it successfully please add a section for it in this article.\\ +There is a Youtube video that shows substantially the same procedure as described below: 
-</WRAP>+https://www.youtube.com/watch?v=Bfmx5NjIWLQ
  
-In this article you will see how to configure your device to become a Wi-Fi extender/repeater/bridge.+The image below shows the normal configuration. 
 +The "main router" is on the right: its WAN port connects to the internet, 
 +and its LAN port (192.168.1.1/24) serves local clients.  
 +The Wi-Fi extender is on the left.  
 +It makes wireless connection (labeled "W-LAN (Client)") as a client to the main router. 
 +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 "upstream" wireless systemWhen this occurs, one approach is to //route// the traffic between LAN and the upstream wireless system. Broadcast traffic, such as DHCP and link-local discovery like mDNS are generally not routable.+\\ {{ docs:guide-user:wifirepeater_802.11-routed-relay.png |}} \\ 
  
-When other options don't work or are too complex to implement, the **relayd** package implements a bridge-like behavior for IPv4 (only), complete with DHCP and broadcast relaying. This configuration can be done through SSH (remote terminal) or through Luci GUI.+Other notes on the configuration:
  
-For the sake of simplicity, I'll call the device we are working on "Wi-Fi extender" from now on.+Even though all end devices on the Wi-Fi extender will get a DHCP address from the main router's LAN subnet, the **LAN** interface of the Wi-Fi extender MUST be on a different subnet for relayd to work (since it is routing traffic, it expects 2 different subnets). 
 +The rest of this article uses 192.168.2.1 as the "Wi-Fi extender subnet".
  
-\\ {{ docs:guide-user:wifirepeater_802.11-routed-relay.png |}} \\ +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 by **relayd** and will be connected to your main network.
  
-This image shows an example setup. **LAN** interface of the Wi-Fi extender device MUST be on a different subnet for relayd to work (since it is routing traffic, it expects different subnets).+The **LAN** interface subnet will be used only as a "management" interface, as devices connecting to the Wi-Fi repeater will be on the main network'subnet instead. If the relayd device becomes unreachable, you will have to configure a PC with a static address in the same subnet as the **LAN** interface (eg. 192.168.2.10 for our exampleto connect and be able to use LuCI GUI or SSH.
  
-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 by **relayd** and will be connected to your main network.+You may use the same Wi-Fi network name (SSID) and encryption, password, etc. 
 +settings on the Wi-Fi extender as your main router. 
 +This allows wireless devices connected to your (wider) network to roam to the best Wi-Fi network.  
 +Alternatively, you can also choose to have a different SSID name/encryption/password on the Wi-Fi extender. 
 +  
 +This procedure has been tested with OpenWrt 23.05.3 
  
-The **LAN** interface subnet will be used only as a "management" interface, as devices connecting to the Wi-Fi repeater will be on the main network's subnet instead. You will have to set your PC with a static address in the same subnet as the **LAN** interface (like 192.168.2.10 for our example) to connect again to the Wi-Fi repeater's Luci GUI or SSH.\\ 
  
-===== 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 ==== 
-=== LAN Interface === +The **LAN** interface of the Wi-Fi extender must be set in a different subnet than the main router.
-As shown in the image above, the **LAN** interface must be set in a different subnet than the Wi-Fi network you are connecting to.+
  
-Begin by configuring and enabling the normal Wi-Fi network and configure it as you want it.\\ +  * Remove any wired connections between your Wi-Fi extender and your main router
-If you are making simple Wi-Fi repeater (device that extends the same Wi-Fi network's coverageit's a good choice to set this Wi-Fi network to be the same as the one of your main router, same name, encryption, password, and so onThis waydevices connected to your (wider) network will automatically stay connected to the best Wi-Fi network.\\ +  * Connect computer with Ethernet to LAN port on the Wi-Fi extender and log into LuCI web UI at 192.168.1.1 (default address) 
-But you can also choose to have a different name/encryption/password if you prefer to.\\ +  * (Optional) Update the firmware of the Wi-Fi extender to the current release. 
-Setting up a Wi-Fi network at this stage is not necessary if you want a "Wi-Fi bridge", a device designed to connect ethernet-only devices to your existing Wi-Fi network.+  * On **System -> Backup/Flash Firmware**click **Perform reset** to return to default OpenWrt settings
 +  * Go to **Network -> Interfaces**, click **Edit** for the LAN interface 
 +  * Set **LAN protocol** to **static address**, click **Change protocol** 
 +  * Assign an IP address using the "Wi-Fi extender subnet(e.g. 192.168.2.1 see image below). Click **Save**. 
 +  * Click **Save and Apply**.
  
-\\ {{ :docs:guide-user:wifirepeater_interfaces_lan.png |}} \\ +\\  {{media:docs:howto:relay_lan_changeip.jpg?400|}} \\
  
-  * Set **LAN protocol** as **static address**  +----
-  * Assign an IP address in a different subnet (e.g. 192.168.2.1) +
-  * Disable DHCP for the **LAN** interface (as it does prevent **relayd** from working).  +
-  * (May be required in certain case) set **Gateway address** and **Use custom DNS servers** using IP address of the primary router (e.g. 192.168.1.1)  +
-  * Save and Apply.+
  
 +  * Reconnect to router at its new IP address (eg. 192.168.2.1)
 +  * From **Network -> Interfaces**, click **Edit** for the LAN interface
 +  * 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 "Ignore interface" box to disable DHCP for the interface.
 +     * On the **IPv6 Settings** tab, choose "disabled" for **RA-Service** and **DHCP-v6 Service**
 +     * 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:docs:howto:relay_lan_disableDHCP.jpg?400|}} \\ 
 ---- ----
-Set your PC's ethernet or Wi-Fi settings at static IP 192.168.2.10 and default gateway 192.168.2.1, then connect again to the wifi repeater (through ethernet or wifi). When you finish all of the following steps, remember to reset your PC's IP address back to the original address (or DHCP), otherwise you won't have Internet access. The repeater won't route traffic from the 192.168.2.0/24 subnet.+\\ {{media:docs:howto:relay_lan_disableIPv6.jpg?400|}} \\ 
  
-=== Wi-Fi === +==== Configure Wi-Fi Interface ====
-We will now set up the client Wi-Fi network, the configuration needed to connect to another Wi-Fi network.\\ Once you are connected again to the Wi-Fi extender, go in the wireless networks page, and click on **Scan** button.\\+
  
-\\ {{ :docs:guide-user:wifirepeater_joinnetwork_wifi_scan.png |}} \\ +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 -> Wireless** page 
 +  * 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.
  
-Choose the Wi-Fi network you want to connect to from the page and click "Join Network".\\ +\\ {{media:docs:howto:relay_join_wifi_1.jpg?800|}} \\  
 +  
 +  * From the list of SSIDs found in the scan, choose the Wi-Fi SSID from the main router and click **Join Network**. 
 + 
 +\\ {{media:docs:howto:relay_join_wifi_2.jpg?800|}} \\   
  
 ---- ----
-\\ {{ :docs:guide-user:wifirepeater_joinnetwork_settings.png |}} \\  
  
-Enter the Wi-Fi password, leave the "name of new network" as "wwan" and select **lan** firewall zone. Click Save.\\+  * You'll see the "Joining Network" pane (image below). 
 +     * Set the "Name of new network" to "wwan" 
 +     * Enter any Wi-Fi credentials such as WPA passphrase 
 +     * Select **lan** firewall zone.  
 +  * Click **Save**. 
 +  * Click **Save & Apply**. 
 + 
 +\\ {{media:docs:howto:relay_join_wifi_3.jpg?600|}} \\ 
  
 ---- ----
-\\ {{ :docs:guide-user:wifirepeater_clientwifi_settings.png |}} \\  
  
-You will land in the client Wi-Fi settings page, set other things as needed.\\ 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 (like in my example) 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 the connection for no reason).+You will see the client Wi-Fi settings page (image below). Edit as required. 
 +The most important settings are on the **Operating Frequency** line. 
 +  
 +  * Set the **Mode** to **Legacy** if you are connecting to a Wi-Fi g networkor **N** if you are connecting to a Wi-Fi n (and so on).\\  
 +  * Set the **Width** to the same channel width as the main router 
 +  * Keep the same Wi-Fi channel number. The extender must match the main router. 
 +  * Click **Save** when finished.  
 +  * Click **Save & Apply**
  
-=== Repeater Interface === +\\ {{media:docs:howto:relay_join_wifi_5.jpg?550|}} \\  
-Go in the **Interfaces** page, we will now add the relayd interface that will join the **lan** and **wwan** interfaces.\\ +==== Remove redundant WAN interface and firewall zones ==== 
-Click on **Add New Interface**.\\+  
 +Although it's optional, it is recommended to delete the redundant WAN interfaces and firewall zones.  
 +  
 +  Go to **Network -> Interfaces** (image below) 
 +  Delete both ''WAN'' and ''WAN6'' 
 +  Go to **Network > Firewall** (image below) 
 +  Delete the ''wan'' rule 
 +  Click **Save & Apply** 
  
-\\ {{ :docs:guide-user:wifirepeater_newinterface.png |}} \\ +**Note:** These actions will also automatically remove any redundant firewall traffic and port forwarding rules.
  
-Write a name for it (**repeater_bridge** is the name I used in the example), and then choose **Relay bridge** in the **Protocol of the new interface** field. Click **Submit**.+\\ {{media:docs:howto:relay_wan_delete.jpg?800|}} \\ 
  
-You may need to reboot your device before the **Relay bridge** option appears.+\\ {{media:docs:howto:relay_firewall_delete_wan.jpg?800|}} \\  
 +==== 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's LAN (eg. 192.168.1.30). 
 +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 
  
----- +  * Go to **Network -> Interfaces** (image below) 
-\\ {{ :docs:guide-user:wifirepeater_relaybridge1.png |}} \\ +  * Click **Edit** for the ''wwan'' interface
  
-In this new interface's setting page, select both **lan** and **wwan** in the **Relay between networks** list.+\\ {{media:docs:howto:relay_wwan_static_1.jpg?800|}} \\
  
-This "Local IPv4 address" (empty in above screen shotsorry, I don't have enough rights to upload a new screen shotneeds to match the IP address assigned by the Wifi-network (egfrom 192.168.1.0/24 range, but do not enter the netmask here!otherwise this bridge will not be accessible from the clients connected directly to the primary router and the relayd-daemon will not start. It makes sense to either fix the IP in the DHCP servers MAC-IP mapping table or configure then WWAN interface of OpenWRT to a fix IP which is not being used in Wifi-networks DHCP-range (I used 192.168.1.2as my DHCP server only serves IP addresses higher than 192.168.1.100)+  * On the **General Settings** tabchange the protocol to 'Static Address' (image below) 
-----+  * Enter an IP address from the main router's LAN subnet (e.g., 192.168.1.30); a subnet mask (e.g., 255.255.255.0)and a gateway IP address, usually the LAN IP address of your main router (e.g., 192.168.1.1)
  
-----+\\ {{media:docs:howto:relay_wwan_static_2.jpg?500|}} \\
  
-\\ {{ :docs:guide-user:wifirepeater_relaybridge2.png |}} \\  +  * On the **Advanced Settings** tab (image below) 
-Move to the Firewall tab of this interface settings page and select **lan**. Click on **Save and Apply**.+  * 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:docs:howto:relay_wwan_statis_3.jpg?500|}} \\ 
 +==== Test Connection ====
  
-----+At this point, the Wi-Fi extender should be wirelessly connected to the main router. 
 +To verify the the connection:  
 +  * Go to **Network -> Diagnostics** 
 +  * 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|}} \\
  
-After you have done this, it might be necessary to reboot the Wi-Fi extender.+==== Install relayd package ====
  
-\\ {{ :docs:guide-user:wifirepeater_final_result.png |}} \\ +  * 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).
  
-This is the final resultNote how the client network has a instead of a IP address.+\\ {{media:docs:howto:relay_package_1.jpg?800|}} \\
  
-=== Firewall ===+\\ {{media:docs:howto:relay_package_2.jpg?400|}} \\
  
-:!: The following part of the configuration should not be necessary (already default options or changed automatically), in case something isn't working check this too. +==== Create Relay Interface ====
  
-\\ {{ :docs:guide-user:wifirepeater_firewall.png |}} \\  +Add the ''relayd'' interface that will join/bridge the **lan** and **wwan** interfacesTo do this: 
-Under the **Network** tab, click on the **Firewall** tabUnder **Zones**, change the forwarding for **lan** and **wwan** to **accept**+  Go to **Network -> Interfaces** 
 +  Click on **Add New Interface** (image below)
  
----- +\\ {{media:docs:howto:relay_create_bridge_3.jpg?500|}} \\ 
-:!: if you are doing this with a device that has a single radio, both Wi-Fi networks will stay on the same channeland total bandwidth will be halved as the same radio is used for 2 different Wi-Fi networks.+  * In the **Add new interface** window (image below) 
 +    * Enter a name ("repeater_bridge" is a good choice) 
 +    * Select **Relay bridge** protocol as shown below. (Reboot your device if the **Relay bridge** option fails to appears.)  
 +  * Click **Create Interface**    
 + 
 +\\ {{media:docs:howto:relay_create_bridge_1.jpg?900|}} \\ 
 + 
 +  * In **Network -> Interfaces**, click **Edit** for the new "repeater_bridge" interface (image below) 
 +    * Enter the IP address assigned to the ''wwan'' interface. (eg. 192.168.1.30)  
 +    * 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.  
 + 
 +\\ {{media:docs:howto:relay_create_bridge_2.jpg?500|}} \\ 
 + 
 +==== Enable the AP ==== 
 +Enable and configure the Wi-Fi extender to be an access point for local devices. 
 + 
 +  * Go to **Network -> Wireless** 
 +  * Click **Edit** button for any item with **ModeMaster**. (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 connection to the main routerensure the **Operating frequency** matches the Client network. 
 +    * Click **Save** 
 +  * **Enable** the wireless network. 
 +  * You might edit/enable other radios (for example, enabling both the b/g/n and n/ac/ax/etc. radios) 
 +  * Click **Save & Apply**. 
 + 
 +==== You're Done - More Testing ==== 
 + 
 +After configuring the Wi-Fi extender's AP, change your computer back to DHCP client mode 
 +and connect to the newly-configured Wi-Fi. 
 +Your computer should be fully on the internethaving acquired a DHCP IP address from your main router.  
 +The Wi-Fi extender can be managed through its static ''wwan'' IP address (eg. 192.168.1.30)  
 + 
 +The **Status -> Overview** window (image below) shows the final result. 
 +''radio1'' is a DHCP client to the main router. 
 +''radio0'' (the access point) has not been configured/enabled yet.  
 +The client Wi-Fi has a ? in the **Host** column instead of a IP address  
 +because its ''wwan'' IP address is only visible in the Network Interfaces page.   
 + 
 +\\ {{media:docs:howto:relay_status_1.jpg?800|}} \\
  
-==== Setup with CLI ====+===== Setup with CLI =====
  
 Before doing any actual configuration, the Wi-Fi interface must be enabled in order to scan for networks in the vicinity: Before doing any actual configuration, the Wi-Fi interface must be enabled in order to scan for networks in the vicinity:
Line 218: Line 330:
 You will likely want to set up your device's Wi-Fi network in a more secure way, as explained in the Wi-Fi setup page [[docs:guide-user:network:wifi:basic|here]]. You will likely want to set up your device's Wi-Fi network in a more secure way, as explained in the Wi-Fi setup page [[docs:guide-user:network:wifi:basic|here]].
  
-==== Accessing the OpenWrt device ==== +===== Troubleshooting ===== 
-If you find the OpenWrt device itself is only accessible from those computers directly connected to the W-LAN AP, not from the ones connected to the OpenWrt W-LAN client, when in the 192.168.1.0 subnet, Make sure the ''Local IPv4 address'' setting in the ''Relay bridge'' interface matches the ip address of the wireless uplink.+==== Accessing the Extender ==== 
 +If you find the Wi-Fi extender itself is only accessible from those computers directly connected to the W-LAN AP, not from the ones connected to the OpenWrt W-LAN client, when in the 192.168.1.0 subnet, Make sure the ''Local IPv4 address'' setting in the ''Relay bridge'' interface matches the ip address of the wireless uplink.
 (The alternative is tedious: It is possible to access the OpenWrt box via its ''192.168.2.1'' address if you manually configure your computer to that subnet.) (The alternative is tedious: It is possible to access the OpenWrt box via its ''192.168.2.1'' address if you manually configure your computer to that subnet.)
 +
 +==== Check Firewall zones ====
 +
 +:!: The following part of the configuration should not be necessary (already default options or changed automatically), in case something isn't working check this too. 
 +
 +\\ {{media:docs:howto:relay_firewallzone_checkLAN.jpg?800|}} \\
 +\\  
 +----
 +\\ {{media:docs:howto:relay_firewallzone_checkLAN_2.jpg?400|}} \\
  
 ==== Adding IPv6 support ==== ==== Adding IPv6 support ====
Line 239: Line 361:
 We suppose that you created a ''wwan'' interface when you joined to the other Wi-Fi network as suggested earlier in this guide; otherwise, change the ''dhcp.wan.interface=…'' line accordingly.\\ We suppose that you created a ''wwan'' interface when you joined to the other Wi-Fi network as suggested earlier in this guide; otherwise, change the ''dhcp.wan.interface=…'' line accordingly.\\
  
-That's it. Restart ''ophcpd'' (LuCI System/Starup page, or ''/etc/init.d/odhcpd restart'') and your IPv6-network should begin to configure itself. Connected IPv6-enabled devices should get their public IPv6 addresses, derived from your public IPv6 prefix, and IPv6 traffic should go through your Wi-Fi extender. +That's it. Restart ''ophcpd'' (LuCI System/Starup page, or ''service odhcpd restart'') and your IPv6-network should begin to configure itself. Connected IPv6-enabled devices should get their public IPv6 addresses, derived from your public IPv6 prefix, and IPv6 traffic should go through your Wi-Fi extender. 
  
 ==== Known Issues ==== ==== Known Issues ====
Line 247: Line 369:
   - DHCP issue caused by Access Point. [[https://forum.openwrt.org/t/relayd-not-forwarding-broadcast-bootp-dhcp-responses/53607/15|OWrt forum]]   - DHCP issue caused by Access Point. [[https://forum.openwrt.org/t/relayd-not-forwarding-broadcast-bootp-dhcp-responses/53607/15|OWrt forum]]
   - Extremely poor upstream transfer speeds with some MT762x devices. [[https://forum.openwrt.org/t/question-xiaomi-mi-r3g-mir3g-5ghz-relayd-19-07-upload-performance/50248|Owrt forum]] [[https://bugs.openwrt.org/index.php?do=details&task_id=2816|Bug Report FS#2816]]   - Extremely poor upstream transfer speeds with some MT762x devices. [[https://forum.openwrt.org/t/question-xiaomi-mi-r3g-mir3g-5ghz-relayd-19-07-upload-performance/50248|Owrt forum]] [[https://bugs.openwrt.org/index.php?do=details&task_id=2816|Bug Report FS#2816]]
-  - Need additional instruction for backdoor to router since once dhcp is disabled on LAN, the router become unreachable+  - [[https://forum.openwrt.org/t/relayd-double-nat-issue/134702/|Devices connected to relayd device cannot be reached.]]  [[https://forum.openwrt.org/t/wifi-bridge-only-outbound-connections-work/135973|2nd possibly similar case]] 
 +  - [[https://forum.openwrt.org/t/how-to-use-openwrt-as-a-wi-fi-repeater-using-a-different-ssid/136177|Cannot enable client and AP on same radio]] 
 +  - Additional instruction for backdoor to router since once dhcp is disabled on LAN, the router become unreachable.  This may occur if there are changes to the wireless access point.  eg. wifi SSID, channel number or security passphrase has changed.\\  
 +     - 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://www.nerd-quickies.net/2019/08/20/setup-lan-wlan-bridge-with-openwrt-luci/|Alternative relayd setup guide ]] 
 +  - Alternative detailed Relayd setup instructions can also be found in section 9.10 of the [[https://www.dropbox.com/sh/c8cqmpc6cacs5n8/AAA2f8htk1uMitBckDW8Jq88a?dl=0|1-OpenWrt-LEDE Installation Guide for HH5A]] 
 +  - IPv6 on macOS 10.15+ does not work with a ULA prefix set on LAN [[https://github.com/openwrt/openwrt/issues/7561]] 
 + 
 +==== Using NAT ====
  
-===== Using NAT =====+**<color #ed1c24>Comment:</color>**  This looks like the basic instructions for configuring a simple [[:docs:guide-user:network:wifi:connect_client_wifi|wireless client]] 
 +\\  
 +\\ 
  
 This method basically puts a second Wi-Fi router in cascade on the first one; i.e. usually this means that the extender's clients will be behind double NAT. This method basically puts a second Wi-Fi router in cascade on the first one; i.e. usually this means that the extender's clients will be behind double NAT.
  • Last modified: 2024/08/31 18:25
  • by richardkiss