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.
How do I add a connection in LuCI and check access?
Check the firmware and local access
cat /etc/openwrt_releasecommand -v apk; command -v opkgdf -h; free; dateInstall the required packages
opkg update && opkg install openconnect luci-proto-openconnect ca-bundleapk update && apk add openconnect luci-proto-openconnect ca-bundleCreate the connection in LuCI
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.Select the actual uplink
occ and wan:uci get network.occ.proto; uci changes networkuci set network.occ.auto='0'uci set network.occ.interface='wan'uci commit networkopenconnect, 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.Check LAN forwarding and the exit path
Connect manually and verify each layer
ifup occubus call network.interface.occ statuslogread -e openconnectip -4 rule showip -4 route show table allifdown occ.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.
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