Putting a VPN on an OpenWrt router can send traffic from several devices through one home connection, including devices that cannot run a VPN app themselves. The router becomes the VPN client, while phones, computers, TVs, and other devices continue to join the usual Wi-Fi network. The setup is more involved than installing an app: firmware support, routing rules, DNS behavior, and a recovery plan all matter. Work through the steps below in order, and keep a way to reach the router locally before changing its network settings.
Check firmware and choose a routing method
OpenWrt is a family of firmware builds rather than one identical interface. Available packages depend on the device model, firmware release, CPU architecture, and image configuration. Before installing anything, sign in to the router’s administration interface and note the exact model and installed release. Check the OpenWrt documentation for that device and release, and confirm that the router has enough storage and memory for the packages you intend to use. A package built for a different release or architecture may not install or run correctly.
Decide whether the router should carry all household traffic through the VPN or only selected devices. A full-tunnel configuration is simpler to reason about: traffic from the chosen home network is routed through the VPN, with an explicit exception for the router’s own connection to the VPN server. Policy-based routing is more flexible but adds rules that can be harder to troubleshoot. It can direct particular clients, subnets, or destinations through the tunnel while leaving other traffic on the regular internet connection.
There are two broad implementation paths. One is to configure a supported VPN protocol directly through OpenWrt’s network and firewall components. The other is to run a compatible proxy client, such as sing-box, and create routing rules around its local interfaces. OpenWrt does not automatically understand every provider subscription format. A link intended for a desktop client may need to be converted or entered through a supported management method; do not assume that pasting any subscription URL into the router will create a working tunnel.
Choose a protocol only after checking what both the service and the router support. WireGuard uses a peer configuration with keys and allowed addresses; OpenVPN uses a profile and may require certificates or authentication details. Shadowsocks, VMess, Trojan, and Hysteria2 are proxy protocols, not interchangeable OpenVPN or WireGuard configuration files. Client support and configuration syntax differ, so use instructions intended for the specific router software and client version. If you use a subscription, treat its URL and credentials as private access information.
120+
Countries covered
190+
Routes listed
Unlimited
Simultaneous devices
14 days
Refund period
These service details do not guarantee that every router can run every client or protocol. If you are considering a service for a router-based setup, first compare the available configuration options with the packages your firmware can actually run. LeleVPN supports Windows, macOS, iOS, Android, and Linux clients; router use depends on compatible software and a configuration method for the specific OpenWrt build.
Prepare packages and connection details
Back up the router configuration before installing packages or editing network and firewall settings. In LuCI, look for the backup or firmware update area and save a copy somewhere other than the router. Also make a note of the router’s local address, Wi-Fi name, and the computer’s current connection method. Keep a device connected by Ethernet if possible. If a firewall rule or route interrupts Wi-Fi access, a wired connection can make recovery much easier.
Use the package manager and package feeds that match the installed firmware. OpenWrt releases can differ in package-management tools, package names, and available interfaces, so consult the documentation for the exact release rather than pasting commands from a guide for another version. Install only the components required by the selected method. For example, a direct WireGuard setup needs WireGuard support and the relevant LuCI interface if you want to configure it through the web UI; an OpenVPN setup needs the OpenVPN package and any required LuCI integration. A proxy-client setup has its own package and configuration requirements.
Before applying changes, gather the connection material from a trusted account dashboard or the service’s official setup instructions. Depending on the protocol, this may include a server address, port, client key, peer key, certificate, authentication details, or a complete profile. Match each value to the field named in the client documentation. Do not put a subscription URL or private key in a public support post, screenshot, or third-party conversion website. If your client supports importing a configuration file, save it with permissions appropriate for a file containing credentials.
For a WireGuard peer, pay particular attention to the interface address, peer public key, endpoint, allowed IP ranges, and keepalive setting if one is specified by the provider. For OpenVPN, confirm whether the profile expects username and password, embedded certificates, or separate certificate files. A client may report that it started even when DNS or route settings are wrong, so a “connected” state alone is not a complete test.
Configure the tunnel and route clients
Start by creating the VPN interface without redirecting the whole household through it. In LuCI or the relevant client interface, add the tunnel details and save the configuration. Confirm that the router can establish the connection and that the VPN interface appears as active. The exact menu names vary by release and installed packages. If you edit configuration files directly, use the syntax documented for that software and validate the configuration before restarting the service.
Next, add the tunnel to the correct firewall zone or firewall policy. A common arrangement is to allow traffic from the home LAN to the VPN zone while preventing unsolicited connections from the VPN zone back into the home network. The router itself also needs a route to reach the VPN endpoint over the ordinary WAN connection; otherwise, the tunnel may fail as soon as its own routing rule takes effect. Check the OpenWrt documentation for the selected client and firewall system rather than copying rules wholesale from another router.
Choose how clients will use the tunnel:
- Whole-LAN routing: Send traffic from the home network through the tunnel. This is easy to explain to household members, but local exceptions and devices that need the ordinary WAN may require additional rules.
- Selected-device routing: Match devices by a stable address or a dedicated subnet, then direct only those clients through the VPN. DHCP reservations can help keep a device’s address consistent.
- Separate Wi-Fi network: Create a distinct network or wireless SSID for devices that should use the VPN. This makes the choice visible to users and can simplify troubleshooting, but requires careful firewall and DHCP configuration.
Apply one routing method first and test with a single computer or phone. Do not enable multiple overlapping policy-routing systems unless you understand which one takes precedence. If you run a proxy client alongside a native VPN interface, establish which component owns DNS, the default route, and firewall marks. Two clients that both try to manage those settings can create loops, leaks, or a connection that appears active while traffic still uses the wrong path.
For a household planning a router-based configuration, LeleVPN VPN for China provides general service information; separately verify that your OpenWrt device and chosen client can use the configuration method you intend. For device-specific installation and account-client instructions, you can also consult the quick-start guide. A desktop or mobile app and a router configuration are different deployment paths, so do not assume that importing a subscription into one automatically configures the other.
Test DNS, local access, and recovery
Test the setup in stages rather than checking only whether a website opens. First confirm that the router itself can reach the VPN endpoint and that the tunnel remains active. Then test one client on the intended network. Check its public IP using a reputable IP-checking service and compare the result with the expected route. Repeat after reconnecting the client and after restarting the router, because a configuration that works only until a reboot is not finished.
DNS deserves a separate check. A client may send web traffic through the tunnel while name lookups continue to use a resolver on the regular WAN, or the reverse. Check which DNS server the client receives from DHCP and whether the VPN client or router is configured to send DNS queries through the intended path. Use a DNS leak test as one diagnostic, but interpret the result in context: browsers may use encrypted DNS settings of their own, and a test reflects the browser and resolver behavior at that moment. If the results do not match the intended design, review DHCP options, router resolver settings, client DNS settings, and policy-routing rules rather than changing several at once.
Test local network access too. Printers, network storage, smart-home hubs, and router administration pages usually need to remain reachable over the local LAN even when internet traffic uses the VPN. If local devices stop communicating, check whether the VPN policy is capturing private LAN address ranges or whether a firewall rule is blocking traffic between the relevant local networks. Keep the management address reachable from a trusted home device, and avoid exposing the administration interface to the public internet as a workaround.
- ✅ Save a known-good configuration before changing firewall or routing behavior.
- ✅ Confirm the VPN interface, client route, and DNS behavior independently.
- ✅ Test local printers and other home devices after enabling the tunnel.
- ✅ Reboot once and verify that the intended routes return automatically.
- ❌ Do not treat a connected icon as proof that every client uses the VPN.
- ❌ Do not run two routing clients that both modify DNS and the default route without a clear design.
If the router becomes unreachable, first reconnect over Ethernet and try the documented local management address. If that fails, use the device-specific OpenWrt recovery procedure and the backup you saved. A reset may erase the current configuration, so use it only when appropriate for the device and after checking its recovery instructions. When the tunnel fails but local access still works, disable the most recent routing or firewall change, restore the previous configuration, and test again before making another adjustment.
OpenWrt router VPN FAQ
Can every OpenWrt router run a VPN client?
No. Support depends on the device, firmware build, available packages, and resources. Check the official device documentation and the requirements of the chosen client before installing packages. A router may support basic networking but lack the storage, memory, or compatible build needed for a particular VPN or proxy client.
Will the router automatically import a subscription link?
Not necessarily. Subscription links can use formats intended for particular apps, and OpenWrt packages do not all support the same formats. Confirm that the router client can consume the provider’s format or follow an official conversion or configuration procedure. Keep the link private because it may grant access to account routes.
Can I route only some home devices through the VPN?
Yes, if your chosen routing setup supports policy-based rules or a separate network. A DHCP reservation, dedicated subnet, or separate Wi-Fi network can make client selection easier to manage. Test with one device first, and document which rule determines whether its traffic uses the VPN or the ordinary WAN.
What should I check if the tunnel connects but sites fail?
Check DNS resolution, the client’s default route, firewall forwarding, the router’s route to the VPN endpoint, and any allowed IP ranges in the VPN configuration. Test local access separately from internet access. Change one setting at a time and keep a known-good backup so you can restore the router if a rule blocks management access.