You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a feature request for binding a SoftEther Server Listener to a specific IPv4 or IPv6 address. Currently, Listener supports binding to a specific socket port number, but it does not support specifying the address. Such a behavior can be useful for a multi-homed system with multiple IP addresses (with a single network adapter or multiple network adapters).
I would find SoftEther Server to be more useful if it could do this, as I would bind SoftEther Server to a loopback address, such as 127.1.2.3, port 8888, and run sniproxy on port 443 to share port 443 with an HTTPS server running on, for example 127.2.3.4, port 8888, and SoftEther Server. To preserve the existing behavior, the socket's host address should bind to 0.0.0.0 and/or :: if it is unspecified. I realize that there are other ways to solve this problem, and after examining at the source code for Listener.c, I realize that the work to do this may be fairly involved. Regardless, thank you for creating SoftEther.
(Alternatively, it'd be a neat feature if SoftEtherVPN Server could support a bypass, reverse proxy mode that connects non-VPN requests to a specified server, relaying the data. But that is likely far out of scope for SoftEtherVPN Server.)
The text was updated successfully, but these errors were encountered:
Hello,
This is a feature request for binding a SoftEther Server Listener to a specific IPv4 or IPv6 address. Currently, Listener supports binding to a specific socket port number, but it does not support specifying the address. Such a behavior can be useful for a multi-homed system with multiple IP addresses (with a single network adapter or multiple network adapters).
I would find SoftEther Server to be more useful if it could do this, as I would bind SoftEther Server to a loopback address, such as 127.1.2.3, port 8888, and run sniproxy on port 443 to share port 443 with an HTTPS server running on, for example 127.2.3.4, port 8888, and SoftEther Server. To preserve the existing behavior, the socket's host address should bind to 0.0.0.0 and/or :: if it is unspecified. I realize that there are other ways to solve this problem, and after examining at the source code for Listener.c, I realize that the work to do this may be fairly involved. Regardless, thank you for creating SoftEther.
(Alternatively, it'd be a neat feature if SoftEtherVPN Server could support a bypass, reverse proxy mode that connects non-VPN requests to a specified server, relaying the data. But that is likely far out of scope for SoftEtherVPN Server.)
The text was updated successfully, but these errors were encountered: