-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
统一 domainStrategy
行为.
#2026
统一 domainStrategy
行为.
#2026
Conversation
感谢 PR, 我觉得这个,茴香豆的茴有几种写法,大可不必。我们文档只写了一种,应该把其它的都删掉,并且 default 报错。 |
正确的. |
adf552d
to
24313e3
Compare
24313e3
to
4634bef
Compare
a353f0c
to
5195f97
Compare
已经做出调整. |
有 localAddr,感觉逻辑不太对, |
现在是配置了 sendThrought 且使用任何一个 IP 相关的 Strategy 时表现为强制解析对应类型的地址且无 Fallback 行为。
|
应遵循文档行为 https://xtls.github.io/config/outbounds/freedom.html#outboundconfigurationobject 只有 UseIP、ForceIP 自动判断 sendTrough,其它的该炸就炸 此外这里也有个 domainStrategy https://xtls.github.io/config/transport.html#sockoptobject , |
This comment was marked as outdated.
This comment was marked as outdated.
我们可以把这里的自适应代码删了,改为在配置解析层面实现,比如说,sendTrough 为 IPv4 时:
|
sendThrough 和 domainStrategy 不在同一层,不动接口的话这个应该没法实现.
我就先按这个来了. |
c73e413
to
a4e80f0
Compare
感谢!先合了 #2719 |
* 统一 `domainStrategy` 行为. * Update proto --------- Co-authored-by: rui0572 <[email protected]>
能不能有一种机制,如果目标服务器同时有v4、v6地址,PreferIPv6的话可以先连接v6地址,如果失败再连接v4地址? |
#2014 (comment)