Outbound 那个 targetStrategy 用的是哪块代码

            strategy := h.config.DomainStrategy
			if destination.Network == net.Network_UDP && origTargetAddr != nil && outGateway == nil {
				strategy = strategy.GetDynamicStrategy(origTargetAddr.Family())
			}
			ips, err := internet.LookupForIP(dialDest.Address.Domain(), strategy, outGateway)

also you can see GetDynamicStrategy in "internet\config.go".

in short, it convert "useIP" to "useIPv4v6" or "useIPv6v4" base on originalDest-IP-type.

for example if originalTarget is IPv4, we use "useIPv4v6" instead of "useIP",

This does not change any logic, because in "useIP" we select a random IP between all-IP-types, and selected-IP can be any type, and "useIPv4v6" is the same, but it prioritize IPv4 to IPv6.

This is necessary so that we don't encounter MTU-problem or GFW-recognize-problem(for freedom)

@RPRX

Regardless of MTU-problem, I found a more important reason:

almost all users bypass domestic websites, but if original-request-IP-type != final-sent-request-IP-type on UDP, they send 1250-bytes-on-IPv6/1230-bytes-on-IPv4, while it should be the other way around and GFW easily detects that the user is using proxy-tools !!!

so we should send to same IP-type as much as possible.

这两个anyip检查又是什么意思

这两个anyip检查又是什么意思

currently, there is no difference between "listen": "" and "0.0.0.0" and "[::]"
in all three cases, we listen on both IPv4 and IPv6 and in all three cases we have "[::]" for UDP-localAddr.

but if we use [::] instead of nil, because [::] is IPv6, we only get IPv6 when we use "useIP"/"ForceIP" strategy:

but this is not correct and we should received both IPv4 and IPv6, because "origin" mean use inbound-local, and inbound-local listen on both IPv4 and IPv6.

///

localAddr is anyIP/anyIPv6 only when network is UDP and we listen on all-interface, so we should use nil instead of [::] to receive both IP-type.

我已经把这个功能标记为不支持udp了 udp上这玩意就是损坏的不应该再管了 而且src也没有这个问题

when UDP is listen on one-interface it works, also we should have this feature for UDP, otherwise we should have multiple-outbounds beside multiple-inbounds, but now we only need to have multiple-inbounds and one outbound with origin is enough.

Nothing has changed except on "origin" when udp listen on one-interface "gateway" set to that, otherwise we don't set gateway(instead of not set at all)

so now by excepting anyIP everything works properly, and there is no need for multiple-outbounds, only multiple-inbounds is needed.

如果你执意那么做应该在udpworker知道hub是anyip之后根据源IP把本地IP重置成正确的0000或者[::]

If you insist on doing that, you should reset the local IP to the correct 0000 or [::] according to the source IP after udpworker knows that the hub is anyip.

I will do it, wait...

如果你执意那么做应该在udpworker知道hub是anyip之后根据源IP把本地IP重置成正确的0000或者[::]

done.

Tested and Ready.

合，都可以合

I did a force-push just to add a neglected line of code

I did a force-push just to add a neglected line of code

目前暂时没有要合的 PR 了，如果你还要改的话可以再 force-push