Have you ever counted how many devices are connected to your home Wi-Fi? Laptop, smartphone, Smart TV, smart speaker, thermostat, video doorbell β and that's not all. Setting up a proxy on each of them individually is a task that takes hours. But there is an easier way: set up the proxy once on the Asus router β and all traffic in the house will automatically go through the desired IP address.
In this article, we will go step by step on how to do this on Asus routers, what types of proxies are suitable for this task, and why smart devices without such protection can become a vulnerability in your network.
Why set up a proxy on the router instead of each device
Most people set up proxies manually β in the browser, in Windows settings, or on their smartphones. This works, but only for one specific device. As soon as you switch to another gadget β everything needs to be repeated.
Now imagine that you have 15-20 devices at home. This is a typical situation for a modern home with smart technology. Some of them do not even have an interface for proxy setup β for example, Xiaomi smart bulbs, Nest thermostats, baby monitors, or voice assistants like Yandex Station or Amazon Echo. They have no browser, no menu with network settings β just a connection to Wi-Fi.
Setting up a proxy at the router level solves this problem once and for all:
- All devices at once β any gadget connected to Wi-Fi automatically uses the proxy.
- No manual setup β no need to dig into the settings of each phone, TV, or tablet.
- IoT devices are also protected β smart speakers, cameras, thermostats, and other gadgets without their own setup interface.
- Centralized management β change the proxy once on the router, and the change applies to all devices.
- Single IP for the entire network β all devices access the internet through one external address, which is important for services that track geography.
For those who use proxies for work purposes β for example, to monitor prices on marketplaces or test advertising campaigns from different regions β router setup is especially convenient. You can allocate a separate Wi-Fi network for work tasks and route it through the proxy without affecting the main home network.
Important to know
Asus routers are among the few consumer routers that support advanced network features right out of the box or through the alternative Merlin firmware. This makes them a popular choice among those who are serious about setting up their home network.
What type of proxy is suitable for the Asus router
Before diving into the router settings, it's important to understand: not every type of proxy can be connected at the router level. Let's explore the options.
HTTP/HTTPS proxy β a limited option
Standard HTTP proxies only work with web traffic. The router cannot "wrap" all network traffic in them because IoT devices, gaming consoles, and smart speakers use not only HTTP but also other protocols. This type is poorly suited for router setup.
SOCKS5 proxy β a working option
SOCKS5 is a more versatile protocol. It operates at the TCP/UDP level and can handle any type of traffic, not just web. That's why SOCKS5 is most often used for router setup. It is supported in the Asus Merlin firmware and some standard firmwares through redsocks or similar utilities.
VPN through proxy β the most convenient way
Many proxy providers offer access through a VPN tunnel (OpenVPN or WireGuard). Asus routers natively support the OpenVPN client β directly in the web interface. This is the simplest way to "wrap" all traffic through a proxy server without complex technical manipulations. Essentially, you connect the router to a VPN that operates over the proxy infrastructure.
| Type | Router support | Covers IoT | Complexity |
|---|---|---|---|
| HTTP proxy | Partial | β No | Medium |
| SOCKS5 | Through Merlin/scripts | β Yes | High |
| OpenVPN (through proxy) | Natively in Asus | β Yes | Low |
| WireGuard | In newer Asus firmwares | β Yes | Low |
If you need to cover all devices without exception β including smart speakers and IoT β choose residential proxies with OpenVPN or SOCKS5 support. Residential IPs are especially important if you want your traffic to appear as that of a regular home user rather than a corporate server.
What you need to know about Asus firmware before setup
Asus routers operate on two main firmwares, and this affects what options you will have for proxy setup.
Standard Asus firmware (Stock Firmware)
The standard firmware comes on all Asus routers out of the box. It supports:
- OpenVPN client β built-in and works without additional settings
- WireGuard β added in firmwares starting from version 3.0.0.4.388 (RT-AX series routers)
- Basic routing rules
- Guest network with separate settings
For most users, the standard firmware is sufficient β especially if you are using an OpenVPN connection to the proxy server.
Asus-Merlin firmware (advanced features)
Asus-Merlin is an unofficial firmware based on the standard one but with enhanced capabilities. It was developed by independent developer Eric Sauvageau and is widely used by advanced users. Merlin adds:
- Script support (including Entware β package manager)
- Ability to install redsocks to redirect traffic through SOCKS5
- Flexible routing rules by IP and domains
- Autostart scripts (post-mount, services-start)
- More detailed control over OpenVPN and WireGuard
If you need maximum control β for example, to route only specific devices or only certain domains through the proxy β Merlin provides that capability. Installing Merlin is no more complicated than updating the standard firmware and does not void the warranty (in most cases).
Tip
Before setting up, update the router firmware to the latest version. This is important for both security and the stability of the VPN/proxy client. You can do this in the Administration β Firmware Upgrade section in the router's web interface.
Which Asus models are suitable
Almost all modern Asus routers support the OpenVPN client. Here are popular models on which the described setup works reliably:
- Asus RT-AX88U, RT-AX86U, RT-AX82U
- Asus RT-AC88U, RT-AC86U, RT-AC68U
- Asus ZenWiFi AX (XT8), ZenWiFi Pro ET12
- Asus RT-AX58U, RT-AX56U
Step-by-step proxy setup on the Asus router
We will consider two main methods: via OpenVPN (easier, for most users) and via SOCKS5 with Merlin (for those who want more control).
Method 1: Connecting via OpenVPN (standard firmware)
This method is suitable if your proxy provider offers access via OpenVPN. Most residential proxy providers offer this option.
Step 1. Obtain the OpenVPN configuration file
Log into your proxy provider's personal account. Find the section with connection settings β it is usually called "VPN," "OpenVPN," or "Configuration." Download the file with the .ovpn extension. It already contains the server address, port, and certificates.
Step 2. Open the router's web interface
Enter the address 192.168.1.1 or router.asus.com in your browser. Enter the administrator login and password (by default β admin/admin, but if you haven't changed them, now is the time to do so).
Step 3. Go to VPN settings
In the left menu, find the VPN section. Go to the VPN Client tab. Click the Add Profile button.
Step 4. Upload the configuration file
Select the connection type OpenVPN. Enter a profile description (for example, "Residential Proxy"). Click Upload Configuration File and select the downloaded .ovpn file. If a username and password are required β enter them in the corresponding fields. Click Activate.
Step 5. Check the connection
After activation, the VPN Client section should show a status of Connected. Now all traffic from all devices in your network goes through the proxy server. Check the IP address from any device in the network β it should match the proxy server's IP.
Method 2: SOCKS5 through redsocks (Merlin firmware + Entware)
This method is more complex but offers more flexibility. It allows you to use SOCKS5 proxy and route all TCP traffic through it.
Step 1. Install Asus-Merlin
Download the Merlin firmware for your router model from the official site asuswrt-merlin.net. Install it via Administration β Firmware Upgrade β the process is identical to updating the standard firmware.
Step 2. Enable SSH and connect to the router
In the web interface, go to Administration β System. Enable SSH access on port 22. Connect to the router using any SSH client (for example, PuTTY on Windows or Terminal on Mac) at the address 192.168.1.1.
Step 3. Install Entware and redsocks
Entware requires a USB drive connected to the router. After connecting and formatting it to ext3/ext4, run the Entware installation with the command:
entware-setup.sh
After installing Entware, install redsocks:
opkg update
opkg install redsocks
Step 4. Configure redsocks
Create a configuration file /opt/etc/redsocks.conf with the following content (replace the data with yours):
base {
log_debug = off;
log_info = on;
log = "file:/opt/var/log/redsocks.log";
daemon = on;
redirector = iptables;
}
redsocks {
local_ip = 0.0.0.0;
local_port = 12345;
ip = YOUR_PROXY_IP;
port = YOUR_PROXY_PORT;
type = socks5;
login = "YOUR_LOGIN";
password = "YOUR_PASSWORD";
}
Step 5. Add iptables rules
Create a script /jffs/scripts/firewall-start that will redirect traffic through redsocks:
#!/bin/sh
# Start redsocks
/opt/sbin/redsocks -c /opt/etc/redsocks.conf
# Create REDSOCKS chain
iptables -t nat -N REDSOCKS
# Exclude local addresses
iptables -t nat -A REDSOCKS -d 0.0.0.0/8 -j RETURN
iptables -t nat -A REDSOCKS -d 10.0.0.0/8 -j RETURN
iptables -t nat -A REDSOCKS -d 192.168.0.0/16 -j RETURN
iptables -t nat -A REDSOCKS -d 127.0.0.0/8 -j RETURN
# Redirect TCP through redsocks
iptables -t nat -A REDSOCKS -p tcp -j REDIRECT --to-ports 12345
# Apply to LAN traffic
iptables -t nat -A PREROUTING -i br0 -p tcp -j REDSOCKS
Make the script executable: chmod +x /jffs/scripts/firewall-start. After rebooting the router, all TCP traffic will go through the SOCKS5 proxy.
Features of proxy operation with IoT and smart devices
Smart devices are a special category. Unlike computers and smartphones, they cannot configure proxies themselves. Thatβs why router-level setup is the only way to route their traffic through the desired IP.
But there are nuances that are important to consider:
Smart speakers (Yandex Station, Amazon Echo, Google Home)
Voice assistants actively interact with the manufacturer's cloud servers. When changing IP through a proxy, some services may require reauthorization or temporarily stop working. This is especially true for geo-dependent functions β for example, Yandex Station may perform worse if the IP address is identified as foreign.
Solution: use residential proxies with IPs from your region, or set up selective routing (see the next section) so that smart speakers work directly.
Smart TVs and streaming devices
Samsung and LG TVs, as well as devices like Apple TV and Chromecast, work great through router proxies. This is a popular application β for example, to access streaming services from other regions. Important: some streaming platforms actively fight against proxies and may block data center IPs. For such tasks, it is better to use residential proxies β they appear as regular home connections and are less likely to be blocked.
Surveillance cameras and intercoms
IP cameras and intercoms often use RTSP and other specialized protocols. SOCKS5 with redsocks covers TCP traffic, so most cameras will work correctly. However, UDP traffic (used by some cameras for video streaming) may not pass through the proxy β this depends on the specific implementation.
Thermostats, smart bulbs, and sensors
Most IoT devices like Xiaomi Mi Home, Philips Hue, or Nest thermostats use HTTPS requests to cloud servers. They work perfectly through OpenVPN proxies on the router. One caveat: if the device is tied to geolocation (for example, a smart lock with geofencing), changing the IP may disrupt this function.
Practical advice
Before switching the entire house to a proxy, test the connection first on one device. Ensure that all necessary functions work correctly, and only then extend the setup to the entire network.
Selective routing: proxy only for necessary devices
It is not always necessary to route all devices through the proxy. For example, you may want your work laptop and Smart TV to operate through the proxy, while the smart speaker and refrigerator use the regular internet connection. This is called split tunneling or selective routing.
Method 1: Policy-based routing in OpenVPN (Merlin)
In the Asus-Merlin firmware, there is a section Policy Rules in the OpenVPN client settings. Here you can specify specific IP addresses of devices in your network whose traffic will be routed through the VPN/proxy. Other devices will continue to operate through the regular connection.
How to set it up:
- Open VPN β VPN Client β your profile β Edit
- Go to the Policy Rules tab
- Enable the Enable Policy Rules option
- Add the IP addresses of the devices that should work through the proxy (for example, 192.168.1.101 for the laptop)
- Save and restart the VPN client
Method 2: Static IPs for devices + iptables rules
For selective routing, it is convenient to assign static IP addresses to the necessary devices. This is done in the Local Network β DHCP Server β Manually Assigned IP section. Specify the MAC address of the device and the desired IP.
After that, in the iptables script (for the redsocks option), you can add exceptions by source IP address:
# Exclude smart speaker (192.168.1.150) from proxy
iptables -t nat -A REDSOCKS -s 192.168.1.150 -j RETURN
# Exclude thermostat (192.168.1.151) from proxy
iptables -t nat -A REDSOCKS -s 192.168.1.151 -j RETURN
Method 3: Separate guest network for proxy
Another elegant way is to create a separate Wi-Fi network (guest) and route its traffic through the proxy, leaving the main network unchanged. Asus routers support up to 3 guest networks on each band (2.4 GHz and 5 GHz).
Practical scenario: create a network "Work_Proxy" and connect your work laptop and devices that need the proxy to it. The main network "Home" operates directly for IoT and smart speakers.
To implement this method in Merlin, a script is used that adds a routing rule for the guest network subnet (usually 192.168.2.0/24) through the VPN interface.
Common problems and their solutions
When setting up a proxy on an Asus router, typical problems may arise. Here are the most common ones and their solutions.
Problem 1: VPN connects, but the internet does not work
Reason: The .ovpn configuration file contains the directive redirect-gateway def1, which redirects all traffic through the VPN, but DNS requests are not configured correctly.
Solution: In the Asus VPN client settings, find the Custom Configuration field and add the line: dhcp-option DNS 8.8.8.8. This will instruct the router to use Google's DNS servers for name resolution.
Problem 2: Proxy works, but speed has dropped 3-5 times
Reason: OpenVPN encryption puts a load on the router's CPU. Budget models with processors up to 800 MHz may struggle with encryption at high speeds.
Solution 1: In the OpenVPN settings, change the cipher from AES-256 to AES-128 or use the WireGuard protocol β it is significantly faster than OpenVPN at the same security level.
Solution 2: Consider using data center proxies for tasks where speed is more important than anonymity β they provide higher bandwidth.
Problem 3: Smart speaker stopped working after proxy setup
Reason: Smart speaker services determine geolocation by IP and block access from "undesirable" regions, or require reauthorization when the IP changes.
Solution: Add the smart speaker's IP address to the routing exceptions (see the section on selective routing). It will work directly, while other devices will go through the proxy.
Problem 4: After rebooting the router, the proxy does not start
Reason: Startup scripts were not saved in permanent memory or do not have execution rights.
Solution: Ensure that the scripts are in the /jffs/scripts/ directory (the router's permanent memory), not in /tmp/ (cleared on reboot). Check permissions with the command ls -la /jffs/scripts/ β all scripts should have the executable file attribute (x).
Problem 5: Some sites block access through the proxy
Reason: Data center IPs are used, which are easily identified as proxies/VPNs by specialized services (MaxMind, IPinfo).
Solution: Switch to residential proxies β their IP addresses belong to real internet providers and home users, so they are significantly less likely to be blocked by sites and streaming platforms.
| Problem | Quick solution |
|---|---|
| No internet after connecting VPN | Add DNS server in custom config |
| Low speed | Switch to WireGuard or AES-128 |
| Smart speaker not working | Add to routing exceptions |
| Proxy does not start after reboot | Scripts in /jffs/scripts/ + chmod +x |
| Blocks on websites | Switch to residential proxies |
Conclusion
Setting up a proxy on an Asus router is one of the most practical ways to provide a single point of internet access for the entire home or office network. You get coverage for devices that physically do not support manual proxy setup: Smart TVs, smart speakers, IoT sensors, cameras, and thermostats.
For most users, the optimal path is OpenVPN through the standard Asus firmware. It is simple, reliable, and works immediately after loading the configuration file. If flexibility is needed β selective routing, SOCKS5, device exceptions β it is worth switching to the Asus-Merlin firmware.
The key point is the correct choice of proxy type. For tasks where it is important to appear as a regular home user (streaming, access to geo-dependent services, protection from blocks), we recommend considering residential proxies β they provide real IPs from home providers and minimal risk of blocks on any platforms. If the priority is speed and stability for monitoring or automation, mobile proxies with a high level of trust from websites and services will suffice.