-
Notifications
You must be signed in to change notification settings - Fork 579
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] MacOS Tun 最新版中没有正确覆盖DNS #439
Comments
party从来就没有将dns设置成“198.18.0.2”过,而是设置成“223.5.5.5” |
那也和你的说法不匹配啊,仍然保留在 DHCP 下发的 DNS 而不是你说的 223.5.5.5 |
@kmahyyg 截图dns设置 |
@kmahyyg 虚拟网卡设置 |
@kmahyyg 发log |
Username and server domain name redacted. Logging level changed to debug.
May I kindly request to reopen this issue for progress tracking purpose? |
Just FYI, affected code should be located mihomo-party/src/main/core/manager.ts Lines 278 to 321 in 7d70008
The output above may be helpful for troubleshooting. Thanks for assistance in advance. |
@kmahyyg 这需要party储存密码,部分人认为这更不安全 |
我觉得可能并不需要,因为:
因为看上去在事实上你已经有一个 root 权限的 sidecar 进程了,需要的只是一个 wrapper,比如在这个进程通过 unix socket 去传入一个 cmd+dns 实现一个 privileged IPC 来改掉 DNS。 然后在用户开启 Fake-IP + Tun 的情况下,自动修改 DNS 到 198.18.0.2 可能是比 223.5.5.5 更好的选择。 |
@kmahyyg 设置为198.18.0.2的话,异常退出会导致无法上网,公共dns则没有这个问题,内核仅仅需要一个能路由到tun的dns地址 |
I agree with @xishang0128 , and for the suggestion of wrapper implementation, please have a consider about that. If you'd choose to ask user to turn off "require an administrator password to access system-wide settings", please add it to the manual and FAQ page on your website for helping poor basxxxd like me. I really appreciate your help regarding this issue and thank you so much for your excellent work. |
Verify steps
操作系统
MacOS
系统版本
15.2 (24C101) ARM64
发生问题 mihomo-party 版本
v1.5.12
描述
在 1.5.10/1.5.11 版本中启用 tun 模式会自动修改当前网卡 DNS 为 198.18.0.2,在 1.5.12 中此功能失效,DNS 仍为原网络下 DHCP 下发的 DNS。
GUI 侧设置中已配置为 接管DNS=True,接管Sniff=True
DNS 配置中 覆盖DNS策略=False,使用系统 Hosts=True,IPv6=False
Sniff 配置启用,覆盖连接地址=False
历史 Issue #80 中有提到会自动配置,实际没有。
重现方式
开启 Tun 模式,DNS 配置为 Fake-IP。
The text was updated successfully, but these errors were encountered: