UDP acceleration feature has been added to the new beta version 1.01.96.
Can you test it and provide feedback?
Feature request for softether protocol
Re: Feature request for softether protocol
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
Re: Feature request for softether protocol
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...
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...
Re: Feature request for softether protocol
Okay, looking very much forward for the next releaseadmin wrote: ↑Wed Jan 15, 2025 9:10 am 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...
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.
Re: Feature request for softether protocol
I did some tests with the SoftEther client and it doesn't seem possible to use UDP acceleration when the connection goes through VPN Azure.
The connection status shows:
Physical Underlay Protocol = TCP/IP via VPN Azure (IPv4)
Protocol Details = IPv4 VPN Azure
UDP Acceleration is Supported = No
UDP Acceleration is Active = No
Please, can you explain better the configuration you are using?
The connection status shows:
Physical Underlay Protocol = TCP/IP via VPN Azure (IPv4)
Protocol Details = IPv4 VPN Azure
UDP Acceleration is Supported = No
UDP Acceleration is Active = No
Please, can you explain better the configuration you are using?
Re: Feature request for softether protocol
Yeah, so on the Server side the Azure VPN relay is enabled and its hostname is used as Remote Server on the VPNClientPro side
On the server side i see:
Physical Underlay Protocol - TCP/IP via VPN Azure (IPv4)
IPv4 VPNAzure UDPAccel_Ver=2 ChachaPoly_OpenSSL UDPAccel_MSS=1309
UDP Acceleration is Supported YES
UDP Acceleration is Active NO
On the client side VPNAzure is set as remote server
TCP:443
Use UDP Acceleration
https://prnt.sc/KwV9Aco_Hx1X
On the server side i see:
Physical Underlay Protocol - TCP/IP via VPN Azure (IPv4)
IPv4 VPNAzure UDPAccel_Ver=2 ChachaPoly_OpenSSL UDPAccel_MSS=1309
UDP Acceleration is Supported YES
UDP Acceleration is Active NO
On the client side VPNAzure is set as remote server
TCP:443
Use UDP Acceleration
https://prnt.sc/KwV9Aco_Hx1X
Re: Feature request for softether protocol
And this is when connecting from Softether Client
Client config https://prnt.sc/daoanq5YxCTz
Client status https://prnt.sc/UleFZAEc6z4J
Server 4.38
Client 4.43
Client config https://prnt.sc/daoanq5YxCTz
Client status https://prnt.sc/UleFZAEc6z4J
Server 4.38
Client 4.43
Re: Feature request for softether protocol
Unfortunately the server I'm using for testing doesn't seem to work like yours.
Please, can you create a test account on your VPN server and send me a address, port, user and password privately so I can do some testing?
For testing, it's enough that the VPN allows me to ping an IP address.
Please, can you create a test account on your VPN server and send me a address, port, user and password privately so I can do some testing?
For testing, it's enough that the VPN allows me to ping an IP address.
Re: Feature request for softether protocol
Sent test credentials in PMadmin wrote: ↑Fri Jan 17, 2025 6:21 pm Unfortunately the server I'm using for testing doesn't seem to work like yours.
Please, can you create a test account on your VPN server and send me a address, port, user and password privately so I can do some testing?
For testing, it's enough that the VPN allows me to ping an IP address.
Update:
Upon further testing I can confirm, that UDP Acceleration does work via Azure Relay if server is not behind CG-NAT
https://prnt.sc/w0OmpocmbhWU