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

Request being able to specify starting port for Wireguard tunnels #1074

Open
k6ccc opened this issue Jan 21, 2024 · 0 comments
Open

Request being able to specify starting port for Wireguard tunnels #1074

k6ccc opened this issue Jan 21, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@k6ccc
Copy link

k6ccc commented Jan 21, 2024

Love the new Wireguard tunnels. One request. Currently a tunnel server always starts Wireguard tunnels starting at port 5525 and counts up from there. It would be handy to be able to specify the starting UDP port for tunnels. Here's the use case. I have two nodes at home that are both capable of being a tunnel server. One is normally used, and the other is a backup. With legacy tunnels (always TCP port 5525), I have two forward rules in my router with one forwarding TCP port 5525 to the primary node and a second forward rule (normally disabled) forwarding TCP port 5525 to the backup node. If I need to use the backup, I have to log into my router and disable the primary rule and enable the forward to the backup node. Of course I can do the same thing with the Wireguard UDP ports, but since each tunnel uses a different UDP port, it would be much simpler if could set up forward rule (for example) ports 5525 - 5534 forward to the primary node, and port 5535 - 5544 forward to the backup node. That would make it easier to have some tunnels normally come into the backup node.

Just as a point of reference, until yesterday I had a second Internet service, so I was able to have the primary node using one ISP and the backup node using the other ISP. Then the forward rules would specify which WAN the packets came in on that would determine the destination. However I killed my cable Internet so I only have one ISP.

@k6ccc k6ccc added the enhancement New feature or request label Jan 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant