leaf
leaf copied to clipboard
Feature process rule
add process rule
sample config:
[General]
dns-server = 223.5.5.5
tun = auto
loglevel = debug
[Proxy]
Direct = direct
SOCKS5 = socks,192.168.0.105,7890
[Rule]
# will match process path containing `curl`
PROCESS-NAME, curl, SOCKS5
# match process by pid
PROCESS-PID, 18868, SOCKS5
FINAL, Direct
- Fetching process information is not always available in different environments such as iOS NE or UWP. What about making it an optional feature, and throw a warning whenever a config contains process rules?
- PID is a volatile identifier. I am wondering whether
PROCESS-PIDrules are really useful...
- Fetching process information is not always available in different environments such as iOS NE or UWP. What about making it an optional feature, and throw a warning whenever a config contains process rules?
- PID is a volatile identifier. I am wondering whether
PROCESS-PIDrules are really useful...
- I will add a warning log later if the rule is not supported
- Find the PID (Process ID) of Telegram, then configure the rule to observe if it can use the proxy.
Find the PID (Process ID) of Telegram, then configure the rule to observe if it can use the proxy.
I think there is a built-in connectivity indicator in the Telegram client? Anyway, users tweaking proxies can always comment out all rules but the FINAL one.