ClashWrt 1.9.6

ClashWrt 1.9.6

• The router's own downloads go through the VPN with either core: update checks, the core, lists and dashboards are fetched through the clashwrt-fetch listener, whose proxy: Proxy key meow-openwrt ignored, so they followed the rules (DIRECT under "direct except the lists") and the update check waited on a slow GitHub. Generated configs now also start their rules with IN-NAME,clashwrt-fetch,Proxy, which every core follows; the bypass set does not count it. The Overview offers once to update the configuration.
• Yandex DNS for Russian sites by default: the wizard turns it on for a config written elsewhere too; it stays off only where a config of ClashWrt's says it was turned off.
• meow-openwrt updates no longer go round in circles: the installed release is read from the package database, so a stale note no longer offers the same update again and again; and an install counts as done when the package is in, since apk 3 fails every run while some unrelated package is broken ("1 error" and nothing else) and the core was in fact replaced.

Full Changelog: v1.9.5...v1.9.6

ClashWrt 1.9.5

v1.9.5

ClashWrt 1.9.4

ClashWrt 1.9.4

• DNS no longer goes REFUSED with domain forwards to the core: with server=/domain/127.0.0.1#1053 entries in dnsmasq (forwards for single domains to the core's port), the general forward to the core was taken as already there and left out while noresolv went on, so every other name was refused. A forward for one domain no longer counts as the general one.
• Telegram as a site brings its addresses along: its clients connect to the data centres by IP, with no lookup and no SNI, so the domain rules alone let that traffic go direct. Adding Telegram as a site (wizard or "Add site") now also writes its networks from core.telegram.org/resources/cidr.txt as IP-CIDR/IP-CIDR6 rules with no-resolve.
• Bypass list: a failed refresh is shown: setctl.sh status names the last refresh that failed and why (WARNING: the last refresh, N minutes ago, failed: ...), instead of only showing the list getting older. A stamp from the future (clock set back) no longer holds the list back for good.

Full Changelog: v1.9.3...v1.9.4

ClashWrt 1.9.3

ClashWrt 1.9.3

• meow-openwrt on more ARMv7 routers: arm_cortex-a15_neon-vfpv4 (IPQ806x), arm_cortex-a9_vfpv3-d16 (mvebu), arm_cortex-a9_neon and arm_cortex-a9 without an FPU (BCM53xx), as meow-openwrt's builds now cover them. Until a meow-openwrt release carries a package for the router's arch, installing it stops with "has no package for " and nothing is changed.
• Less flash with meow-openwrt's fast direct: the config's domains are neither parsed nor kept (config-domains.list was 1.2 MB on flash with nothing to read it), since the core judges them itself. With mihomo they are kept as before.

Full Changelog: v1.9.2...v1.9.3

ClashWrt 1.9.2

ClashWrt 1.9.2

• Wizard: Russian sites through Yandex DNS are on by default. The category-ru domains are resolved by Yandex over DoH, so they point at nearby CDN nodes; the set is used for DNS only, never for routing.
• Firewall: blocking QUIC (UDP/443) is on by default. Browsers fall back to TCP, which the proxy carries more reliably where UDP is throttled.
• Firewall: blocking DNS-over-HTTPS to public resolvers is on by default, so browsers with built-in DoH fall back to the router's DNS.

Existing installs keep their current block_quic/block_doh values in /etc/config/clashwrt; turn them on in Settings.

Full Changelog: v1.9.1...v1.9.2

ClashWrt 1.9.1

ClashWrt 1.9.1

• Installer: no dnsmasq-full question with meow-openwrt. The core fills the bypass set from its own DNS answers (dns.nftset), and the stock dnsmasq only forwards to it, so dnsmasq-full is needed only with mihomo and "direct except the lists".

Full Changelog: v1.9.0...v1.9.1

ClashWrt 1.9.0

ClashWrt 1.9.0

• Proxies page in LuCI: the core's groups, the node each one uses, a click to switch and a delay test — no web dashboard needed (it costs 8 MB of flash). The router asks the core itself, so the controller may stay on 127.0.0.1 and the secret never reaches the browser.
• Fast direct with meow-openwrt (dns.nftset): under "direct except the lists" the core adds the address of every DNS answer its rules send to a proxy to the bypass set — GEOSITE, keyword and rule-set domains included — so everything else is forwarded by the kernel. No domain list in dnsmasq (about 30 MB of RAM with mihomo on a large config) and no dnsmasq-full needed.
• config.yaml keeps only the current mode's inbounds: ports a mode does not use are commented out with their numbers kept, an unused tun is switched off, and both come back when the mode changes (mihomo reloads, meow-openwrt restarts).
• Auto picks TPROXY with meow-openwrt too, by the same kernel test as with mihomo; switching the core keeps the mode.
• dnsmasq → core → AdGuard Home: while the core has to see every lookup, dnsmasq forwards to it alone; another general upstream is left out meanwhile and put back afterwards. Pick Local resolver (AdGuard Home etc.) as the core's DNS in the wizard to keep AdGuard Home filtering.
• The watchdog's DNS fallback no longer counts per-domain servers as an upstream.
• Release notes are written from the commits when a tag carries none.

Full Changelog: v1.8.0...v1.9.0

ClashWrt 1.8.0

Full Changelog: v1.7.0...v1.8.0

ClashWrt 1.7.0

Full Changelog: v1.6.4...v1.7.0

ClashWrt 1.6.4

Full Changelog: v1.6.3...v1.6.4