Extending wireless network coverage often becomes a pressing issue in modern homes with thick walls or large areas. Using standard router firmware doesn't always provide the desired results, as functionality is limited by the extender's basic capabilities. OpenWrt provides a flexible toolkit that allows you to turn any compatible router into a powerful signal repeater.
Unlike simple repeaters, which often halve speed, properly configured Linux-based systems allow you to create a stable bridge between access points. You'll need a basic understanding of network protocols and a second router operating in client mode. This is the scenario we'll explore in detail in this article.
The setup process may seem daunting to a beginner due to the lack of a graphical interface at the initial stages, but the results are worth it. You'll gain full control over your network interfaces and the ability to fine-tune the radio module's settings. LuCI — The web interface we will be using makes it much easier to manage after the initial installation of packages.
Preparing equipment and selecting the operating mode
Before you begin tinkering with the software, you need to clearly determine which relay method will be most effective in your situation. There are two main approaches: using the WDS (Wireless Distribution System) or configuring a client in conjunction with a bridge. The first option requires support from the main router, which isn't always the case.
The second option, where an OpenWrt device acts as a regular WiFi client and then distributes internet over its own network or bonds interfaces, is more universal. It works with virtually any primary router, regardless of brand and firmware. For this method to work, it's critical that the network interfaces are properly forwarded.
⚠️ Warning: Before flashing the firmware, make sure your router model is fully compatible with the OpenWrt version. Using an unsupported image may brick the device.
Frequency band selection is also important. If you plan to use a single radio frequency for both receiving and transmitting, network speed will inevitably drop by approximately half due to the half-duplex operation of the radio. The ideal solution is to have two radio modules: one receiving the signal on 5 GHz, the other transmitting on 2.4 GHz, or vice versa.
- 📡 WDS mode: requires support on both sides, provides transparent bridging at the MAC address level.
- 💻 Client mode (Station): Universal, the router receives an IP like a regular device, requires NAT or bridging configuration.
- ⚡ Dual-band circuit: eliminates speed drops by using different frequencies for traffic input and output.
OpenWrt installation and initial configuration
The initial stage involves installing the operating system on the device. If the firmware is already installed, you can skip this step and proceed directly to updating the package database. The installation process is specific to each model and often requires the use of a utility. TFTP or the factory firmware web interface to download the image .bin or .sysupgrade.bin.
After successful boot, the system has a default IP address 192.168.1.1You need to connect your computer to the router's LAN port and configure a static IP on the network card, for example, 192.168.1.2Access to the command line is provided via the protocol SSH, there is no default password.
ssh root@192.168.1.1
The first thing you need to do after logging in is change your root password and update your repository lists. This will ensure security and access to the latest versions of packages. Enter the command passwd to change the password, and then opkg update to update the package manager metadata.
Next you need to install the web interface LuCI, if it wasn't installed automatically during firmware installation. This will significantly simplify future configuration of network bridges and wireless interfaces through the graphical menu, rather than relying solely on console configuration files.
opkg install luci
After installing the web interface, you need to start the service uhttpd, which is responsible for the web server. This usually happens automatically after a reboot, but to be sure, you can run the command /etc/init.d/uhttpd enable And /etc/init.d/uhttpd start.
Configuring the wireless interface in client mode
Now let's move on to the most important step: configuring the wireless module to receive a signal from the main access point. In the LuCI web interface, go to the section Network → WirelessHere you will see a list of available radio modules (radio0, radio1).
Click the button Scan next to the desired radio module. The system will scan the air and display a list of available networks. Find your primary network in the list and click the button Join NetworkThis action will automatically create a new network interface and configure basic connection settings.
⚠️ Attention: When connecting to a network with MAC address filtering (Whitelist), do not forget to add the MAC address of the new repeater router to the settings of the main router, otherwise the connection will be blocked.
In the interface settings window that opens (usually it gets the name wwan (or similar) you must specify the security type and password for your primary WiFi network. Make sure the correct encryption algorithm is selected, most often it is WPA2-PSK or WPA3-SAE for modern networks.
An important point is the firewall configuration. The new interface must be assigned to a zone. wanto ensure traffic is correctly routed from the external network to the internal network. If you plan to create a single bridge (switch mode), the configuration will be different and will require creating a bridge interface.
- 🔐 Encryption: strictly corresponds to the settings of the main access point.
- 🌐 Firewall Zone: Usually WAN for router mode, LAN for bridge mode.
- 📶 Channel Width: It is better to leave it on Auto or set it manually for stability.
☑️ Checking client settings
Organization of a bridge (Bridge) or NAT
Once a WiFi internet connection is established, you need to decide how exactly the repeater will distribute the signal. There are two fundamentally different approaches. The first is NAT (Network Address Translation), where the repeater creates its own subnet. The second is bridge mode, where all devices are on the same network.
Mode NAT It's easier to set up and often works out of the box after joining the network. In this case, devices connected to the repeater will see the internet, but devices connected to the main router (such as printers or media servers) may not. This isolates the repeater's network segment.
To organize the regime Bridge (single namespace), you need to create a new interface of the "Bridge device" type. In the settings of this interface (Network → Interfaces → Add new interface) select the "Unmanaged" or "Static address" protocol, and add LAN ports and the previously created WiFi client (wwan) to the physical settings.
The key here is to disable the DHCP server on the repeater. In bridge mode, only the main router should be distributing IP addresses. Leaving DHCP enabled on both devices will cause a network conflict, and all clients will lose internet access.
| Parameter | NAT mode (Router) | Bridge Mode (Access Point) |
|---|---|---|
| Repeater IP address | Static on WAN or own subnet | Static on the main router network |
| DHCP server | On | Turned off |
| Access to resources | Limited (needs pass-throughs) | Full (as in a local network) |
| Difficulty of setup | Low | Average |
Why is there sometimes no internet in bridge mode?
A common mistake is forgetting to disable the DHCP server on the repeater. If two devices attempt to assign IP addresses, clients receive incorrect gateways. Second, the repeater itself has an incorrect IP address; it should be a free IP in the main network range, but outside the main router's DHCP pool.
Optimizing connection speed and stability
Even with the logical portion configured correctly, the physical layer can make its own adjustments. To minimize speed losses in repeater mode, it's critical to select the correct channel and channel width. Using channel width 40 MHz or 80 MHz in a noisy environment can lead to greater packet losses than a narrow channel in 20 MHz.
It is also worth paying attention to the transmission power (txpower). Maximum power doesn't always mean the best signal; it can cause intermodulation distortion and clog the receiver. Experimentally reducing the power to 17-20 dBm often results in a more stable link.
To diagnose connection quality, use the utility iwinfo. It will show the signal level (signal) and noise level (noise). The difference between them (SNR) is the main indicator of quality. The higher the SNR, the higher the actual data transfer rate.
iwinfo wlan0 scan
The entered command will display a list of networks and their parameters. Pay attention to the column SignalValues closer to 0 (for example, -50 dBm) are better than values like -80 dBm. If the signal is too weak, no software optimization will help; you'll need to adjust the antenna placement or the device itself.
Additional features and security
OpenWrt allows you to implement features unavailable in stock firmware. For example, you can set up a guest network isolated from the main one or implement traffic filtering. VPN packages can also be installed, allowing you to encrypt all repeater traffic.
Security is an important aspect of management. By default, after installing LuCI, access to the web interface can only be opened on LAN ports, but if you have a complex bridged setup, double-check your firewall rules. Make sure the port 80 or 443 does not stick out towards the WAN interface without protection.
To automatically reconnect when the connection to the main router is lost, you can use scripts or built-in watchdog mechanisms. However, the standard mechanism wpad (WPA Supplicant) in OpenWrt is quite reliable and will automatically try to re-establish the connection if control packets are lost.
- 🛡️ Firewall: Set up rules to restrict access to the admin panel.
- 🔌 VPN Client: Raise the tunnel directly on the repeater to protect all devices.
- 📊 Monitoring: install the package vnstat to track traffic.
⚠️ Note: Interfaces and package names may vary slightly between different OpenWrt versions (for example, from 19.07 to 23.05). Always consult the official documentation for your version if the standard paths don't work.
Frequently Asked Questions (FAQ)
Is it possible to use an OpenWrt router as a universal repeater for any network?
Yes, in client mode (Station), it will connect to any WiFi network with the password. However, if the primary network uses specific corporate authentication methods (802.1x EAP-TLS, etc.), configuration will require manual editing of the wpa_supplicant configuration files.
Why is the speed through an OpenWrt repeater lower than directly?
This is a physical limitation of the wireless channel. The radio module cannot simultaneously receive and transmit data on the same frequency (half-duplex). Speed drops by at least a factor of 2. The only solution is to use two different radio modules (5 GHz backhaul, 2.4 GHz uplink).
How do I reset my router if I lose access to it?
Use the physical reset button on the case. With the power on, press and hold it for 10-15 seconds until the LEDs flash. This will reset the IP address. 192.168.1.1 and an empty root password.
Should DHCP be disabled on the main router?
No, DHCP must remain enabled on the main router if you're configuring Bridge mode. You should disable the address server on the OpenWrt device to avoid network conflicts.