[Bug Report] pname(qbittorrent) 非 must 出站会导致 qbittorrent 无法连接 tracker
sommio opened this issue · comments
Checks
- I have searched the existing issues
- I have read the documentation
- Is it your first time sumbitting an issue
Current Behavior
pname(qbittorrent) direct 会导致 qbittorrent 无法连接 tracker
# DNS配置
ipversion_prefer: 4
upstream {
dnspub: 'udp://119.29.29.29:53'
cloudflare: 'tcp://1.1.1.1:53'
}
routing {
request {
qname(geosite:cn) -> dnspub
fallback: cloudflare
}
}
# cat /etc/resolv.conf
nameserver 119.29.29.29
nameserver 223.5.5.5
nameserver 223.6.6.6
nameserver 127.0.0.1
# 无法连接 tracker
pname(NetworkManager) -> direct
dip(224.0.0.0/3, 'ff00::/8', geoip:private) -> direct
pname(qbittorrent-nox) -> direct
pname(qbittorrent) -> direct
# 正常工作
pname(NetworkManager) -> direct
dip(224.0.0.0/3, 'ff00::/8', geoip:private) -> direct
pname(qbittorrent-nox) -> must_direct
pname(qbittorrent) -> must_direct
# 另一个正常工作路由,但似乎没有按期望全局走 dae dns
dip(geoip:private) -> direct
pname(NetworkManager, systemd-resolved) -> direct
pname(qbittorrent-nox) -> must_direct
pname(qbittorrent) -> must_direct
Expected Behavior
与 must_direct 一样可以正常链接 tracker
Environment
- Daed version: daed v0.4.0rc1
- OS: Arch Linux
- Kernel: 6.6.25-2-cachyos-lts-lto
- Others: daed-bin-x64-v3 from archlinuxcn
Anything else?
使用其它非 must 出站也会重现此问题,虽无法连接 tracker 但均可上传
pname(NetworkManager) -> direct
dip(224.0.0.0/3, 'ff00::/8', geoip:private) -> direct
pname(qbittorrent-nox) -> must_direct
pname(qbittorrent) -> must_direct
Thanks for opening this issue!
@sommio 这个会导致 dns 查询使用 cloudflare,但是由于 pname 是 qbittorrent,dns 会使用 direct,建议 routing 前面对 1.1.1.1 设置 proxy
感谢 mzz,问题解决了
pname(NetworkManager) -> direct
dip(224.0.0.0/3, 'ff00::/8', geoip:private) -> direct
dip(1.1.1.1) -> proxy
pname(qbittorrent-nox, qbittorrent) -> direct