Frequently Asked Questions ​

Here we have some common questions people ask. If you have any questions not listed here, feel free to open an issue.

Which release should I use for my system? ​

Here are some common systems that people use Clash on, and the recommended release for each of them:

• NETGEAR WNDR3700v2: mips-hardfloat #846
• NETGEAR WNDR3800: mips-softfloat #579
• ASUS RT-AC5300: armv5 #2356
• MediaTek MT7620A, MT7621A: mipsle-softfloat (#136)
• mips_24kc: #192

If your device is not listed here, you can check the CPU architecture of your device with uname -m and find the corresponding release in the release page.

List of wontfix ​

The official Clash core project will not implement/fix these things:

• Snell
• Custom CA
• VMess Mux
• VLess
• KCP
• mKCP
• TLS Encrypted Client Hello
• TCP support for Clash DNS server
• MITM

The following will be considered implementing when the official Go QUIC library releases.

• TUIC
• Hysteria

Proxies work on my local machine, but not on my router or in a container ​

Your system might be out of sync in time. Refer to your platform documentations about time synchronisation - things will break if time is not in sync.

Time complexity of rule matching ​

Refer to this discussion: #422

Clash Premium unable to access Internet ​

You can refer to these relevant discussions:

• #432
• #2480

error: unsupported rule type RULE-SET ​

If you stumbled on this error message:

FATA[0000] Parse config error: Rules[0] [RULE-SET,apple,REJECT] error: unsupported rule type RULE-SET

You're using Clash open-source edition. Rule Providers is currently only available in the Premium core. (it's free)

DNS Hijack does not work ​

Since tun.auto-route does not intercept LAN traffic, if your system DNS is set to servers in private subnets, DNS hijack will not work. You can either:

1. Use a non-private DNS server as your system DNS like 1.1.1.1
2. Or manually set up your system DNS to the Clash DNS (by default, 198.18.0.1)