Advanced Networking FAQ
Covers Clash issues in LAN, router, Docker, NAS, IPv6, UDP, WireGuard, Hysteria, and TUIC setups, with the ports, routes, and permissions to check first in each environment.
Follow the actual network path into the problem
LAN, router, Docker, IPv6, and UDP issues must be evaluated against the network topology.
What Commonly Goes Wrong with LAN Sharing, Routers, or Docker Deployments?For LAN or container deployments, verify listen addresses, routes, DNS, subnet bypasses, network mode, exposed controls, direct private routing, and least privilege.What If LAN Devices, Printers, a NAS, or the Router Admin Page Are Unreachable?LAN access problems usually mean a private subnet is being proxied, fake-ip is not excluding internal domains, TUN routes are capturing too much traffic, or the browser proxy is not bypassing local addresses.What If Game, Voice, QUIC, or UDP Traffic Is Not Working?UDP support depends on the client, core, node protocol, network environment, and rules, so an HTTP test alone is not enough. Check the node declaration, selected policy group, TUN capture, and UDP logs together.Why Do Some Clients Not Support VLESS, Hysteria, TUIC, or WireGuard?Protocol support depends on the core implementation and client integration. The original Clash, Clash Meta/Mihomo, and different clients do not support the same set of protocols.