Setting up OpenWrt as a WiFi client: WDS client

Using a router under control OpenWrt As a wireless client, this is a powerful solution for extending network coverage without running long cables. It's common to have an existing internet access point in one part of a home or office, but a distant room has a weak or nonexistent signal. In such cases, a second router can act as a receiver, capturing the signal over the air and distributing it to connected devices via LAN ports or its own wireless network.

Unlike standard firmware, where functionality is often limited, OpenWrt Provides flexible tools for creating complex network configurations. Client mode allows you to turn virtually any compatible router into a universal adapter. This is especially useful for devices without built-in WiFi, such as older Smart TVs, game consoles, or desktop computers, that need to connect to a provider's wireless network.

The configuration process requires careful attention, as it involves changing the default behavior of network interfaces. You'll need to combine the physical WAN port (which will become part of the bridge) and the wireless interface into a single logical structure. Despite the apparent complexity, following the steps carefully will allow you to implement the project in 15-20 minutes, even with minimal Linux system administration experience.

Equipment preparation and compatibility testing

Before changing the configuration, you need to ensure that your hardware supports the required operating mode. Not all WiFi modules are capable of operating in client mode (Station mode) while simultaneously distributing the network, although most modern chips do. Atheros And MediaTek They handle this task without any problems. It's critical that the device you'll be connecting to (the main router) and the client (OpenWrt) support the same encryption standards and frequency ranges.

To get started, you will need access to the web interface. LuCI Or, command line skills via SSH. The second option is preferred by experienced users, as it allows for faster diagnosis of connection errors. Make sure your OpenWrt device is running the latest firmware version, as older builds may contain bugs that interfere with stable WDS operation.

Gather the following information about the primary network you will be connecting to:

• 📡 The exact network name (SSID), case-sensitive.
• 🔐 Encryption type (usually WPA2-PSK or WPA3-SAE).
• 📶 Operating frequency (2.4 GHz or 5 GHz) and channel.
• 🌐 MAC address of the main access point (optional, for filtering).

⚠️ Note: If your primary router uses MAC address filtering, you will need to enter the MAC address of your OpenWrt router's WAN interface in the primary device's settings before pairing.

Basic configuration of the wireless interface

The first step is to reconfigure the wireless module. By default, OpenWrt operates in Access Point mode, so we need to change that logic. Go to the menu Network → Wireless in the LuCI interface. You'll see a list of available radio modules. Find the one you plan to use for receiving the signal and click the button. Edit or Scan to search for networks.

Using the scanning feature greatly simplifies the process by allowing you to select the desired network from a list. Once you've selected the target network, the system will prompt you to create a new configuration. In the settings window that opens, ensure that the operating mode (Mode) is set to the value Client or StationThis parameter switches the device from distribution mode to reception mode.

Next, you need to configure the security settings. Tab Wireless Security requires specifying the correct encryption type. Most often, this is WPA2-PSKIn the key field, enter the password for your primary WiFi network. Even a single character error will result in an infinite loop of connection attempts, which can be tracked in the system logs.

After saving the settings, the wireless interface will attempt to associate with the access point. You can check the connection status in the same Wireless section, where the signal quality indicator and the name of the connected network should appear. If the status shows associated but there is no IP address, which means the problem lies at the network settings level, not the radio channel.

Creating a bridge between WAN and WiFi

The most important step is to bridge the interfaces. By default, OpenWrt separates the WAN (Internet) and LAN (Local Area Network). To ensure the router passes WiFi traffic to its LAN ports, you need to create a bridge. Go to the section Network → InterfacesWe need to edit the WAN interface or create a new one that will be responsible for connecting to the external network.

In the settings of the interface that you configured as a WiFi client, find the field Physical Settings (Physical settings). Here you need to check the box next to the wireless interface you created earlier (usually it's called wwan or has the name of your network). It is also recommended to enable the option Bridge interfaces, if it is available in your version of LuCI, and add the port there eth1 (if you want the router's WAN port to also work as an input, although this is rarely used in client mode).

config interface 'wan'
option proto 'dhcp'
option device 'wwan'

IP Address Acquisition Protocol (Protocol) most often left DHCP Client, since the main router will automatically assign an address to your OpenWrt device. However, if the network is static, select Static address and manually enter the IP, gateway, and DNS. After applying the settings, the interface should receive an IP address from the primary network range.

⚠️ Important: Make sure the IP address of the LAN interface of the OpenWrt router itself does not match the default gateway address. For example, if the main router has an address of 192.168.1.1, it is best to redirect the OpenWrt LAN port to 192.168.1.2 or change the subnet to 192.168.2.1 to avoid conflicts.

Setting up Firewall and Security Zones

After creating the bridge, you need to properly configure the firewall. In the standard OpenWrt configuration, the WAN zone prohibits incoming connections but allows outgoing ones. Since your "WAN" is now a WiFi client, the logic should remain the same: devices on your local area network (LAN) should have internet access but be hidden from the outside network.

Go to Network → Firewall. Check which zone your new interface is assigned to (usually it is zone wan). Make sure that WAN zone is enabled. Masquerading (NAT) if you want all devices behind your router to access the internet under a single IP address. In most cases, NAT should be enabled for client mode so that the main router sees only one device—your OpenWrt router.

Is NAT needed in client mode?

If you're simply expanding your network and want all devices to be on the same subnet (flat network), you can disable NAT, but you'll need to configure routing correctly on the main router. For simple internet access, it's best to leave NAT enabled.

An important point is to check the rules ForwardingThe LAN zone must be allowed to forward traffic to the WAN zone (LAN -> WAN). If the internet doesn't appear on connected devices, try temporarily disabling the firewall for diagnostics. If the network works, the issue lies with the packet filtering rules.

For advanced users, it might be useful to add a rule allowing ICMP (ping) from the WAN zone to the LAN zone if you plan to monitor the availability of devices from the external network, but for home use, this is redundant and reduces security.

Diagnostics and analysis of connection logs

If the connection is not established, don't panic. The system OpenWrt has powerful logging tools. First, check out the section System → System Log or use the command logread in the console. Look for entries related to wpad or hostapd - These demons are responsible for wireless connection.

A common problem is mismatched encryption parameters. In the logs, this will appear as a cycle: "associating," "authenticating," "deauthenticating." This means that a handshake is occurring, but the keys don't match or the encryption type is incorrect. It's also worth checking whether your primary router has MAC address filtering or a client limit.

Speed ​​and stability optimization

Once connected, it's time to fine-tune the settings to achieve maximum performance. By default, OpenWrt may select conservative compatibility settings. In the wireless section, try changing the operating mode (Mode) With Legacy on 802.11ac or 802.11ax, if the equipment supports it. It also makes sense to fix the channel width (20/40/80 MHz) to avoid dynamic bandwidth throttling.

To reduce latency (ping) and improve video stream stability, you can disable the WiFi module's power saving mode. This can be done by adding parameters to the configuration file or through additional settings in LuCI, if available in your driver. uapsd (Unscheduled Automatic Power Save Delivery) is often best kept off for clients that require constant activity.

Keep in mind that dual-band routers can experience difficulties when they attempt to simultaneously receive a signal on one frequency and transmit it on the same one. This phenomenon is called interference. The ideal operating scheme is to receive on 5 GHz and transmit on 2.4 GHz (or vice versa), or to use different channels with a large frequency spacing. If your router only supports one radio module, the network speed will be divided in half between receiving and transmitting.

Why doesn't the router see the 5 GHz network?

You may have the wrong region (Country Code) selected in your country. Some 5 GHz channels are not allowed in all countries. Check your region settings in Wireless → Advanced Settings. Also, make sure your main router isn't using a 160 MHz channel width if the client module doesn't support it.

How do I reset my WiFi settings if I lose access to my router?

If you've made a mistake in the settings and lost access, use the physical Reset button on the device. A short press (usually 5-10 seconds) while the power is on will restore factory settings, preserving installed packages but resetting the configuration.

Can OpenWrt be used as a repeater?

Technically, client mode (WDS-Client) is the basis of a repeater. The only difference is that a repeater also broadcasts an SSID. In OpenWrt, this is accomplished by creating a separate network (SSID) on the same physical interface or a virtual interface bound to the same radio.