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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: