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
Right now the only way to control which IPs are going through a tunnel is with an AllowedIPs list of networks.
However, the most typical need is to allow everything except a certain private range. If we want to create a list of all IPs except, say 192.168.0.0/24, the list is going to be very long and for some people not easy to create or understand. It would be much easier for the user and more efficient for processing if we add an ability to specify something like:
Right now the only way to control which IPs are going through a tunnel is with an AllowedIPs list of networks.
However, the most typical need is to allow everything except a certain private range. If we want to create a list of all IPs except, say 192.168.0.0/24, the list is going to be very long and for some people not easy to create or understand. It would be much easier for the user and more efficient for processing if we add an ability to specify something like:
[Peer]
AllowedIPs = 0.0.0.0/0
ExcudedIPs = 192.168.0.0/16
The logic would be to check first that the IP is in Allowed list and then if it is not excluded
The text was updated successfully, but these errors were encountered: