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
Is your feature request related to a problem? Please describe.
As a user, I do not necessarily want to send all of my traffic down an OpenVPN tunnel. I want to optionally send specific cidrs down the tunnel, and route the rest out through my primary gateway.
Today, this is not possible with the linux-cli, as the list is exclusionary only.
Both models have their benefits, but for minimizing complexity, supporting a model whereby I can specificy what i want to tunnel would be desirable.
Describe the solution you'd like
Additional parameter in pvpn-cli.cfg to augment split_tunell
split_tunnel_exclusive (bool) (determine if the list read from split_tunnel.txt should be considered authoritative on the cidrs to tunnel, or to exclude from the tunnel)
Describe alternatives you've considered
Using other VPN clients adhering to the openvpn standard that can accomplish this (pfSense currently supports this model with their provider)
Additional context
Currently, I split tunnel at my edge and am considering moving to a model where it happens on a host and the edge is ignored. This isn't possible without loads of extra work on the split_tunnel functionality inside the linux-cli today.
I only want to send a handful of cidrs down the vpn, and route the rest out my default gateway.
The text was updated successfully, but these errors were encountered:
I usually don't like commenting without adding anything to the discussion, but this is such a useful feature I want this suggestion to get more of the developer's attention.
Is your feature request related to a problem? Please describe.
As a user, I do not necessarily want to send all of my traffic down an OpenVPN tunnel. I want to optionally send specific cidrs down the tunnel, and route the rest out through my primary gateway.
Today, this is not possible with the linux-cli, as the list is exclusionary only.
Both models have their benefits, but for minimizing complexity, supporting a model whereby I can specificy what i want to tunnel would be desirable.
Describe the solution you'd like
Additional parameter in pvpn-cli.cfg to augment split_tunell
split_tunnel_exclusive (bool) (determine if the list read from split_tunnel.txt should be considered authoritative on the cidrs to tunnel, or to exclude from the tunnel)
Describe alternatives you've considered
Using other VPN clients adhering to the openvpn standard that can accomplish this (pfSense currently supports this model with their provider)
Additional context
Currently, I split tunnel at my edge and am considering moving to a model where it happens on a host and the edge is ignored. This isn't possible without loads of extra work on the split_tunnel functionality inside the linux-cli today.
I only want to send a handful of cidrs down the vpn, and route the rest out my default gateway.
The text was updated successfully, but these errors were encountered: