Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bind Listener to specific IPv4/IPv6 address #1927

Open
jdstroy opened this issue Nov 15, 2023 · 1 comment
Open

Bind Listener to specific IPv4/IPv6 address #1927

jdstroy opened this issue Nov 15, 2023 · 1 comment

Comments

@jdstroy
Copy link

jdstroy commented Nov 15, 2023

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.)

@officialh1
Copy link

Seconded. You might be able to pull this off with Docker as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants