Xray-core: [ BUG ] Wireguard Chain speed problem
unlike sing-box, speed is very slow when chaing wireguard-outbound (using dialerProxy) to another outboundin xray-core, unlike sing-box (using detour).
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 4
- Comments: 20 (10 by maintainers)
It is not a wireguard issue. If it was then a normal wireguard would be affected too.
We must see how both
detouranddialerProxydo traffic routing to different outbound.For UDP, we can test with VLESS-quick and see if it behaves like wireguard as both are udp based protocol.
I think it may hurt other configs that use dialerProxy, I haven’t looked into a proper fix yet. It’s probably a good idea to test it a bit with things like fragment and other common scenarios that may use dialerProxy.
I don’t know. I stopped using it When I saw poor performance.
I just opened this issue to tell devs that sing-box is doing chains with better performance.
The doc statement is probably for when we use kernel wireguard.
I have the same problem. Wireguard over Vmes works very slowly (dialerProxy or proxySettings tag). Xray Wireguard client - 16 Mbit/s Xray Vmes client - 30 Mbit/s Xray Wireguard via Vmes - 50 Kbit/s and lag. Sing-box Wireguard via Vmes (detour) - 25 Mbit/s
OS Windows 10 x64 Xray-core v1.8.6