Feature request for softether protocol

[admin]

UDP acceleration feature has been added to the new beta version 1.01.96.
Can you test it and provide feedback?

[Elezorn]

Fingers crossed on seeing UDP acceleration in changelog someday

And that day is today
Sorry for not answering earlier

So first and foremost, can't thank you enough for continuously improving the APP.

UDP Acceleration runs fine when connecting to a server via DirectIP:
Server side: https://prnt.sc/NfmHVPWAVx0v
Client side: https://prnt.sc/_iUdOqeZO9Y3
I don't have a ultrafast connection at my disposal, so can't really say are there any speed/stability improvements/downgrades. But it works and doesn't seem to break anything. So that's a win) Will continue to observe


However, i guess it can't quite figure correct IP when trying to connect via Azure Relay(Server behind CG-NAT, DirectIP is not possible):
Server side: https://prnt.sc/EfVuoZHgjPeT
Client side: https://prnt.sc/NsdkHdum75Of
Scheme https://prnt.sc/NTDFpJZiegJm

It seems like it's trying to establish direct UDP connection with SE-Server, but treats server's LAN IP as if it is WAN, i don't know

I also noticed a bug, that if there are more than one remote servers present inside one Connection and one server is TCP with UDP Accel, while the other one is NAT-T, than VPN Client will try to establish UDP link using 0.0.0.0 as Server's IP, when connecting via TCP. Disabling UDP Accel or Second server solves the problem
Second remote server disabled: https://prnt.sc/_iUdOqeZO9Y3
Second remote server enabled: https://prnt.sc/x729Jtn9JEwV

[admin]

Thanks for the info.
At the moment the app always uses the ip address sent by the server ("udp_acceleration_server_ip"), when the server is behind a NAT this address is a private ip and therefore cannot be used.
The problems will be solved in the next release...

[Elezorn]

Thanks for the info.
At the moment the app always uses the ip address sent by the server ("udp_acceleration_server_ip"), when the server is behind a NAT this address is a private ip and therefore cannot be used.
The problems will be solved in the next release...

Okay, looking very much forward for the next release
Just to be clear, the test server that's behind CG-NAT is actually accessible with UDP Accel through Azure Relay both via SoftEther desktop Client and Cascade connection initiated by another SE Server.