What is this?
OpenClash is a Mihomo (Clash) client plugin for OpenWrt routers: it runs a policy-based proxy on the router, routing traffic through flexible rule configurations.
OpenClash is a Mihomo (Clash) client plugin for OpenWrt routers: it runs a policy-based proxy on the router, routing traffic through flexible rule configurations.Is this a desktop app, or does it live on my router?It lives on the router — OpenClash installs on OpenWrt as an IPK/APK package and plugs into LuCI, the router's web admin interface.
It lives on the router — OpenClash installs on OpenWrt as an IPK/APK package and plugs into LuCI, the router's web admin interface.How do I get it onto my router?Download the IPK or APK package from the project's download page and install it on OpenWrt; the full usage manual is in the Wiki.
Download the IPK or APK package from the project's download page and install it on OpenWrt; the full usage manual is in the Wiki.What does the router need to have installed first?Quite a few OpenWrt packages: luci, dnsmasq-full, bash, curl, ipset, ip-full, ruby with ruby-yaml, unzip, plus a set of iptables/nftables kernel modules.
Quite a few OpenWrt packages: luci, dnsmasq-full, bash, curl, ipset, ip-full, ruby with ruby-yaml, unzip, plus a set of iptables/nftables kernel modules.Any install gotchas I should know about?Yes — several features need extra modules: TUN mode requires kmod-tun, PROCESS-NAME rules need kmod-inet-diag, firewall4 devices need kmod-nft-tproxy, and Luci >= 19.07 needs luci-compat.
Yes — several features need extra modules: TUN mode requires kmod-tun, PROCESS-NAME rules need kmod-inet-diag, firewall4 devices need kmod-nft-tproxy, and Luci >= 19.07 needs luci-compat.Will it run on any Linux box, or strictly on OpenWrt?Strictly OpenWrt — it is a LuCI plugin built from the OpenWrt SDK, so it targets OpenWrt routers rather than desktop Linux or other systems.
Strictly OpenWrt — it is a LuCI plugin built from the OpenWrt SDK, so it targets OpenWrt routers rather than desktop Linux or other systems.Which proxy protocols does it support?Shadowsocks, ShadowsocksR, VMess, Trojan and Snell, among others — the bundled Mihomo core handles the protocols while OpenClash supplies the rules and routing policy.
Shadowsocks, ShadowsocksR, VMess, Trojan and Snell, among others — the bundled Mihomo core handles the protocols while OpenClash supplies the rules and routing policy.What proxy core does it run under the hood?Mihomo by MetaCubeX is the core engine; OpenClash itself is a LuCI plugin whose code is based on frainzy1477's Luci For Clash.
Mihomo by MetaCubeX is the core engine; OpenClash itself is a LuCI plugin whose code is based on frainzy1477's Luci For Clash.Can I watch what the proxy is doing in real time?Yes — the project uses the zashboard and yacd control panels, and also credits SukkaW's IP check and lmc999's streaming-unlock detection as companion tools.
Yes — the project uses the zashboard and yacd control panels, and also credits SukkaW's IP check and lmc999's streaming-unlock detection as companion tools.What are similar projects?Open-Box, 3X-UI_KIT, fanqiang, nyx, clash-rules, clash, panda-vpn-pro, edgetunnel
Open-Box, 3X-UI_KIT, fanqiang, nyx, clash-rules, clash, panda-vpn-pro, edgetunnelWhich topics is it in?openclash, transparent-proxy, openwrt, mihomo, vmess, clash, firewall, router, v2ray, shadowsocks, dns, censorship-circumvention
openclash, transparent-proxy, openwrt, mihomo, vmess, clash, firewall, router, v2ray, shadowsocks, dns, censorship-circumvention