fakedns+others does not work

[Losalado]

          不要使用 `fakedns+others`，因为 `fakedns+others` [从来就没有正常工作过](https://github.com/v2fly/v2ray-core/blob/2a22a8579d485498b2f423af5073fcbcb784c351/app/dispatcher/sniffer.go#L64-L66)。

1b0e046 使得 fakedns+others 与 fakedns 效果相同（但也不是预期的工作方式），但是 82c42fc 和 3c0aff7 又改坏了。
strings.HasPrefix(protocolString, p) || strings.HasSuffix(protocolString, p) 与 strings.HasPrefix(protocolString, p) || strings.HasPrefix(p, protocolString) 可不是一回事。

Originally posted by @dyhkwong in #2973 (comment)

[Losalado]

#2973
Could anyone fix fakedns+others issue?

[dyhkwong]

This is because content sniffers skip unsupported network,

v2ray-core/app/dispatcher/sniffer.go

Lines 64 to 66 in b7d02ad

	if si.network != network {
	continue
	}

but fakedns+others does not specify network, so it will always be skipped.

It is indeed possible to fix this, but fixing this may break current the semantics of other sniffers, especially routing.rules.protocol also uses the protocol value from sniffing. I think new interfaces or methods may be needed.

[Losalado]

This is because content sniffers skip unsupported network,

v2ray-core/app/dispatcher/sniffer.go

Lines 64 to 66 in b7d02ad

	if si.network != network {
	continue
	}

but fakedns+others does not specify network, so it will always be skipped.

It is indeed possible to fix this, but fixing this may break current the semantics of other sniffers, especially routing.rules.protocol also uses the protocol value from sniffing. I think new interfaces or methods may be needed.

thanks for your info.
Actually when I follow document to configure fakedns+others, it does not work. We may need to add note for fakedns+others if it does not work as document now. Of course, it is the best to achieve function we expected.

[zeddit]

想请问 fakedns+others 是否已经正确修复，V2Ray 5.21.0 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.23.2 linux/amd64) 好像还是无效的。