Advanced Matching Rule
Chute supports several advanced matching rules for fine-grained traffic control.
SUBNET
Rule matches based on network subnet attributes. Uses KEY:VALUE syntax.
SUBNET,TYPE:WIFI,Proxy
SUBNET,SSID:MyWiFi,DIRECT
SUBNET,BSSID:00:11:22:33:44:55,Proxy
SUBNET,ROUTER:192.168.1.1,DIRECT
Supported keys:
| Key | Description |
|---|---|
TYPE |
Network type (e.g. WIFI, CELLULAR, WIRED) |
SSID |
Wi-Fi SSID name |
BSSID |
Wi-Fi access point BSSID (MAC address) |
ROUTER |
Router/gateway IP address |
HOSTNAME-TYPE
HOSTNAME-TYPE,AAAA,Proxy
Rule matches if the DNS record type of the request matches. Useful for routing IPv4 and IPv6 traffic differently.
Common values: A (IPv4), AAAA (IPv6), CNAME.
IN-TYPE
IN-TYPE,SOCKS5,Proxy
Rule matches based on the inbound connection type. Supported values:
| Value | Description |
|---|---|
HTTP |
HTTP proxy inbound |
SOCKS5 |
SOCKS5 proxy inbound |
TUN |
TUN/VIF interface inbound |
IN-USER
IN-USER,user1,Proxy
Rule matches based on the inbound authentication username. Useful when Chute is configured with multiple inbound proxies with different credentials.
IN-NAME
IN-NAME,my-proxy,Proxy
Rule matches based on the named inbound proxy configuration. Useful when running multiple proxy server instances with different names.