iPhone 17 pro max v26.6.1 - app Clash v1.0.4 (68) / Hako core v1.19.30
The app is promising, but I have two questions / concerns :
-
Built-in “DIRECT” profile
The built-in DIRECT profile uses 223.5.5.5 and 1.1.1.1 as DNS servers. It appears to be impossible to modify or replace this profile: importing a custom YAML configuration does not change it. Is this intentional? If so, could you provide a way to customize the DNS settings of the built-in DIRECT profile ?
-
Unexpected UDP/443 blocking rule
My custom profile does not contain any rule blocking UDP port 443, and there is nothing configured under Override or Routing Rules. However, the Runtime Configuration automatically contains:
AND,((NETWORK,udp),(DST-PORT,443)),REJECT
This effectively blocks QUIC/HTTP3. Is this rule intentionally injected by the app? If so, could you explain why, especially when prefer-h3: true is configured for DoH ?
Overall, I would appreciate clarification on whether these two behaviors are intentional or bugs.
iPhone 17 pro max v26.6.1 - app Clash v1.0.4 (68) / Hako core v1.19.30
The app is promising, but I have two questions / concerns :
Built-in “DIRECT” profile
The built-in DIRECT profile uses 223.5.5.5 and 1.1.1.1 as DNS servers. It appears to be impossible to modify or replace this profile: importing a custom YAML configuration does not change it. Is this intentional? If so, could you provide a way to customize the DNS settings of the built-in DIRECT profile ?
Unexpected UDP/443 blocking rule
My custom profile does not contain any rule blocking UDP port 443, and there is nothing configured under Override or Routing Rules. However, the Runtime Configuration automatically contains:
AND,((NETWORK,udp),(DST-PORT,443)),REJECT
This effectively blocks QUIC/HTTP3. Is this rule intentionally injected by the app? If so, could you explain why, especially when prefer-h3: true is configured for DoH ?
Overall, I would appreciate clarification on whether these two behaviors are intentional or bugs.