📘 OpenWrt setup guide

How do I connect Yunoc on an OpenWrt router?

If you know LuCI / SSH, install OpenConnect and its LuCI protocol package, then add the connection and set its outbound interface. Check access on both the router and LAN devices.

Last updated · All platform guides

How do I add a connection in LuCI and check access?

1

Check the firmware and local access

This route is for users familiar with LuCI / SSH. Make sure you can recover through a local wired connection; do not change routes over your only remote connection. Check the version, free space and installed package manager. Do not infer these from a Kwrt or vendor version number alone:
Systemcat /etc/openwrt_release
Package managercommand -v apk; command -v opkg
Resources and clockdf -h; free; date
2

Install the required packages

Use only the set matching this firmware and its repositories. If both managers are present, or neither is available, consult the firmware instructions first:
opkgopkg update && opkg install openconnect luci-proto-openconnect ca-bundle
apkapk update && apk add openconnect luci-proto-openconnect ca-bundle
Do not mix repositories from other releases or bulk-upgrade system packages. Check the clock and keep certificate verification enabled. If LuCI does not show the protocol after installation, follow the firmware instructions to refresh the page or reload rpcd.
3

Create the connection in LuCI

Under Network → Interfaces, create an unused interface named occ and select the OpenConnect / AnyConnect protocol. Leave automatic startup off for now. Enter the complete address shown for Cisco / openconnect on Connection Info, your email and your connection password — not your website password. Preserve the port, path and query; add https:// only once. Leave certificate-login fields empty and do not enter an unknown fingerprint to bypass verification. Do not overwrite an existing interface. Review pending changes before saving and applying, but do not start it yet. Keep passwords out of shell history and support messages.
4

Select the actual uplink

Find the logical uplink interface in LuCI: it may be wan, wwan or another name, not the physical device name. If the form lacks this option, use SSH. These commands apply only after verifying occ and wan:
Check protocol and pending changes firstuci get network.occ.proto; uci changes network
Disable automatic startupuci set network.occ.auto='0'
Set the verified uplinkuci set network.occ.interface='wan'
Saveuci commit network
The protocol must be openconnect, with no unrelated pending changes. The uplink dependency is intended to keep the connection server reachable over WAN. Check it together with the full URI, then verify the active route.
5

Check LAN forwarding and the exit path

Check the actual firewall zones in Network → Firewall. A common setup adds occ to the existing WAN outbound zone; verify LAN forwarding, IPv4 masquerading and MSS settings. A separate zone needs these checked too. Do not rename zones by index, disable the firewall or expose management services on WAN. Review changes before applying and keep local recovery access. MSS adjustment does not replace checking the actual MTU. This is not a kill-switch configuration: disconnection may return traffic to your broadband connection.
6

Connect manually and verify each layer

Start only the verified interface:
Connectifup occ
Statusubus call network.interface.occ status
Loglogread -e openconnect
Policy rulesip -4 rule show
Active routesip -4 route show table all
Check in order: tunnel transmit/receive → DNS and HTTPS on the router → browsing and exit path on a LAN device. Connected status or a successful ping is not enough. Connect the test phone only to this router’s Wi-Fi; turn off mobile data and its own proxy. An upstream management computer retaining its broadband exit is expected. Check IPv4 and IPv6 separately; do not assume every flow is handled. Enable automatic startup only after verification. To stop, use ifdown occ.
7

Connected, but nothing loads?

Show troubleshooting: no receive traffic, LAN failures or stalled pages

No receive traffic and the router is offline: check the full https:// URI, the actual uplink and the server route over WAN. An empty hostname in adding host dependency for at ... is a clue to URI parsing, not proof of an authentication error. Check policy routing too; do not delete the WAN gateway or permanently pin the server IP.

The router works, but LAN devices do not: check their gateway and DNS, then the loaded forwarding / NAT rules, guest networks and other routing tools. On fw4 firmware, nft list ruleset is a read-only check. A page setting does not prove the rule is loaded.

Ping or chat works, but HTTPS stalls: first rule out certificate, destination and DNS problems, then check the runtime device MTU. The form’s 1406 may only be a placeholder; --mtu requests a value from the server, not proof that the device uses it. Find the actual l3_device in interface status, refresh its device page or run ip -s link show dev "ACTUAL-DEVICE".

Comparing MTU values: record the original settings and change one thing at a time. If the runtime value still differs after saving the interface MTU and reconnecting, configure that same device only if the firmware supports it. Do not change WAN/LAN or create a new bridge. 1406 worked in the supplied Kwrt case; it is not a universal recommendation. If the old process keeps reporting Failed to write incoming packet: I/O error after applying the change, stop with ifdown occ and start with ifup occ. Recheck MTU and HTTPS on both router and LAN. If it does not help, restore the original values; remove a device entry only if this experiment created it and nothing else uses it.

Authentication, certificate or transport errors: stop repeated authentication attempts and check the connection password, plan and session allowance. For certificate errors, check the clock, address and trust store; do not bypass verification. Compare no_dtls separately only after routing, DNS and MTU checks, and restore its original state. Plain TCP is not guaranteed to be more reliable.

The member Docs Center’s “OpenWrt router guide” has the full steps and recovery instructions. Redact email, complete connection addresses and credentials before sharing logs; do not send a full configuration containing passwords.
⚠️ Advanced, self-service router setup
This uses community packages, not our own router firmware. We have referenced one Kwrt 25.12 snapshot case; this does not validate all models or long-term reconnection.
These steps troubleshoot a global IPv4 connection. PAC / return routing, IPv6 and DNS paths depend on firmware and local policy. A website switch does not prove split routing is active on the router.
Username and connection password are recommended. Certificate setup requires separate expiry and renewal management. Verify connection status, router access and LAN access separately.

Guides for other platforms

Not sure which routing mode to use? See Global, PAC and Return compared. Something not working? Go to the Help Center.

One account for your devices

On Windows, macOS and Android, sign in to Yunoc with your website account, sync your lines and connect. For other clients, open "Connection Info" for setup instructions. Contact support if you need help.

Sign In / Register