Open linnuxx opened 3 weeks ago
Thank you for your testing. It would be more helpful if you could provide complete data and various tests of controlled variables. Otherwise, we won't be able to do anything.
I am not familiar with wireguard and rathole, so I cannot provide any additional advice.
Thank you for your testing. It would be more helpful if you could provide complete data and various tests of controlled variables. Otherwise, we won't be able to do anything.
ratholeserver:
[server]
bind_addr = "0.0.0.0:8388" # 2333
specifies the port that rathole listens for clients
[server.services.my_nas_ssh]
type = "udp"
token = "key" # Token that is used to authenticate the client for the service. Change to an arbitrary value.
bind_addr = "0.0.0.0:51821" # 5202
specifies the port that exposes my_nas_ssh
to the Internet
nodelay = true
ratholeclient:
[client]
remote_addr = ipvps:8388" # The address of the server. The port must be the same with the port in server.bind_addr
[client.services.my_nas_ssh] token = "key" # Must be the same with the server to pass the validation local_addr = "192.168.1.237:51820" # The address of the service that needs to be forwarded nodelay = true type = "udp"
wireguard over rathole - so performance does not drop much. wireguard over frp - There is less performance through frp, although the vps performance is sufficient to withstand 80-100mbps.
Bug Description
What could be the matter? wgserver mtu 1300. wgclient mtu 1300. frps/frpc are installed on debian12. go version go1.22.2 linux/amd64.
frpc Version
0.57.0
frps Version
0.57.0
System Architecture
linux/amd64
Configurations
frps.toml
bindPort = 7000
frpc.toml
serverAddr = "ipvps" serverPort = 7000
[[proxies]] name = "wg" type = "udp" localIP = "192.168.1.237" localPort = 51820 remotePort = 51821 transport.useCompression = true
Logs
No response
Steps to reproduce
...
Affected area