Closed ariadarkkkis closed 1 week ago
Thanks for your comments. Regarding the first part, it can be done and will be added soon, along with Port Range settings. However, I disagree with the second part, as determining the destination IP on the server side increases packet header size and conflicts with the general backhaul policy. Backhaul is designed to manage a very high number of connections with minimal packet header size.
I have a suggestion for Ports section of Server config:
In this example, port 4000 of the server will be set to LISTENING state and forward all the traffic from this port to 5201 of the client. Then on the client, you can use forwarder to send traffic coming to 5201 to any port or address on the client like the following:
My suggestion is to have bind address in
Ports
config. Like the following:This is useful for server with multiple IP addresses and also useful if there is a custom load balancer running on the server side.
Better way to do this is just like FRP. Have the ports configuration on the client side, so the client choose what ports to open on server and then forward them to a port on the local network of the clinet as follow:
This way, the client opens a port on
1.2.3.4
IP address of the server and opens4000
port and then forward the traffic to127.0.0.1
of the client local network on port5200
.This way, the whole port configuration and forwarding will be done on client side without need any modification on server side.