-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] redir-host 模式无ipv6,以及其他dns配置问题 #1546
Comments
日志等级你忘改了... |
debug太大了,没发复制,我上传文件吧 |
我是只要开tun,就都无法直连ipv6 |
配置关闭tun也没ipv6(只要是redir-host模式),并且此配置只能 redirect[tcp] + tun[udp] 才能使用。我并不知道到是什么原因导致的,还是哪个配置写错了 |
分别访问给出结果 |
~ $ curl -v https://ipv6.google.com * Host ipv6.google.com:443 was resolved.
* IPv6: 2404:6800:400a:813::200e
* IPv4: (none)
* Trying [2404:6800:400a:813::200e]:443...
* connect to 2404:6800:400a:813::200e port 443 from fdfe:dcba:9876::1 port 42596 failed: Connection timed out
* Failed to connect to ipv6.google.com port 443 after 31517 ms: Couldn't connect to server
* Closing connection
curl: (28) Failed to connect to ipv6.google.com port 443 after 31517 ms: Couldn't connect to server
~ $ curl -v https://[2606:4700:4700::1111]
|
没有任何劫持 IPv6 流量发生,你具体用 TUN?iptables? |
有劫持吧,配置文件里开了tun, iptables 不太清楚,我只知道这个模式使用不了v6 ,这次测试的完整日志放下面了 time="2024-09-26T12:37:31.570888114+08:00" level=debug msg="[Rule] use default rules"
time="2024-09-26T12:37:31.573125145+08:00" level=debug msg="[Process] find process beacons.gcp.gvt2.com error: process not found"
time="2024-09-26T12:37:31.573528114+08:00" level=info msg="[UDP] 198.18.0.0:46138 --> beacons.gcp.gvt2.com:443 match RuleSet(reject) using 🚫广告拦截"
time="2024-09-26T12:37:33.224612957+08:00" level=debug msg="[Rule] use default rules"
time="2024-09-26T12:37:33.225524571+08:00" level=debug msg="[Process] find process beacons2.gvt2.com error: process not found"
time="2024-09-26T12:37:33.226190457+08:00" level=info msg="[UDP] 198.18.0.0:38040 --> beacons2.gvt2.com:443 match RuleSet(reject) using 🚫广告拦截"
time="2024-09-26T12:37:56.407652115+08:00" level=debug msg="Hopped to 172.233.81.251:28093"
time="2024-09-26T12:37:56.523638885+08:00" level=debug msg="Hopped to 172.233.81.251:24036"
time="2024-09-26T12:37:56.548022167+08:00" level=debug msg="Hopped to 172.233.81.251:24731"
time="2024-09-26T12:37:56.709627062+08:00" level=debug msg="Hopped to 172.233.81.251:20448"
time="2024-09-26T12:37:57.06474425+08:00" level=debug msg="Hopped to 172.233.81.251:24389"
time="2024-09-26T12:37:57.561044927+08:00" level=debug msg="Hopped to 172.233.81.251:26604"
time="2024-09-26T12:37:57.589465448+08:00" level=debug msg="Hopped to 172.233.81.251:26497"
time="2024-09-26T12:37:57.595693833+08:00" level=debug msg="Hopped to 172.233.81.251:26474"
time="2024-09-26T12:37:57.699663052+08:00" level=debug msg="[Sniffer] Sniff tcp [198.18.0.0:38862]-->[183.47.121.90:80] success, replace domain []-->[szextshort.weixin.qq.com]"
time="2024-09-26T12:37:57.699890604+08:00" level=debug msg="[Rule] use default rules"
time="2024-09-26T12:37:57.700007218+08:00" level=debug msg="[DNS] resolve ipv6.google.com AAAA from "
time="2024-09-26T12:37:57.700712166+08:00" level=debug msg="[DNS] resolve ipv6.google.com AAAA from tls://[2606:4700:4700::1111]:853"
time="2024-09-26T12:37:57.700805135+08:00" level=debug msg="[Rule] use default rules"
time="2024-09-26T12:37:57.701294041+08:00" level=debug msg="[DNS] resolve ipv6.google.com AAAA from tls://8.8.8.8:853"
time="2024-09-26T12:37:57.701366854+08:00" level=debug msg="[DNS] resolve ipv6.google.com AAAA from tls://1.1.1.1:853"
time="2024-09-26T12:37:57.701430031+08:00" level=debug msg="[DNS] resolve ipv6.google.com AAAA from tls://[2001:4860:4860::8888]:853"
time="2024-09-26T12:37:57.701591437+08:00" level=debug msg="[Rule] use default rules"
time="2024-09-26T12:37:57.702778989+08:00" level=debug msg="[Rule] use default rules"
time="2024-09-26T12:37:57.702842322+08:00" level=debug msg="[Rule] use default rules"
time="2024-09-26T12:37:57.702855708+08:00" level=debug msg="[Process] find process szextshort.weixin.qq.com error: process not found"
time="2024-09-26T12:37:57.705871645+08:00" level=debug msg="[DNS] resolve ipv6.google.com A from "
time="2024-09-26T12:37:57.705948885+08:00" level=debug msg="[DNS] resolve ipv6.google.com A from tls://8.8.8.8:853"
time="2024-09-26T12:37:57.705977947+08:00" level=debug msg="[Rule] use default rules"
time="2024-09-26T12:37:57.70890175+08:00" level=debug msg="[DNS] resolve ipv6.google.com A from tls://[2001:4860:4860::8888]:853"
time="2024-09-26T12:37:57.708975447+08:00" level=debug msg="[Rule] use default rules"
time="2024-09-26T12:37:57.716812218+08:00" level=debug msg="[DNS] resolve ipv6.google.com A from tls://[2606:4700:4700::1111]:853"
time="2024-09-26T12:37:57.71691576+08:00" level=debug msg="[Rule] use default rules"
time="2024-09-26T12:37:57.720832479+08:00" level=debug msg="[DNS] resolve ipv6.google.com A from tls://1.1.1.1:853"
|
切换gvisor栈即可,可能Android的问题 |
换成gvisor栈确实可以了 |
以前的版本我能开system和mixed ipv6正常 目前新的几个版本都只有gvisor可以用ipv6 而且使用system和mixed之后会导致一部分ipv6的路由出现问题只能重启解决 |
Arch Linux w/ tproxy. |
@Kimiblock 使用tun测试,而不是非内核处理流量导入的tproxy |
@xishang0128 TUN 模式工作. 但我想用 |
@Kimiblock tun正常就无关内核 |
Makes sense |
在我的机器上, 问题出在 |
Verify steps
Operating System
Android
System Version
android 14 QPR3
Mihomo Version
Prerelease-Alpha
Mihomo Meta alpha-a4e84f0 android arm64 with go1.23.1 Wed Sep 25 07:11:27 UTC 2024
Use tags: with_gvisor
Configuration File
Description
redir-host模式没有ipv6,在 test-ipv6.com 和 ipleak.net 测试ipv6都不通
fake-ip模式则正常
Reproduction Steps
使用 redirect[tcp] + tun[udp]


切换redir-host模式ipv6超时
切换fake-ip模式ipv6正常


Logs
The text was updated successfully, but these errors were encountered: