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
Hi, first of all, thanks so much for your work on vpn-slice! This project has been invaluable to me in regaining some control in the face of corporate VPN mandates.
While it is not a big deal, I frequently like to tweak what hosts are going to the openconnect VPN connection, and what goes directly to my default route. I span a custom configuration file to do this, which gets passed to the vpn-slice parameters whenever I execute my VPN script. However, authenticating with the VPN unfortunately requires 2FA in my case, so restarting it is not convenient.
It would be great if I could start the openconnect VPN tunnel, then spawn a separate process for vpn-slice that sets up the routes, so I can reload that vpn-slice instance whenever I like and have my routing configuration updated. This would all be transparent to the VPN connection, which would keep running happily in the background.
How hard is this? Is it already possible with some hacks? It may be out of scope for vpn-slice, and I understand if this is the case. Maybe a project could wrap and daemonize vpn-slice to produce the desired behaviour?
p.s. if you add some donation link to the project's README, I would love to buy you a coffee for your work. :)
Thanks
The text was updated successfully, but these errors were encountered:
Hi, first of all, thanks so much for your work on
vpn-slice
! This project has been invaluable to me in regaining some control in the face of corporate VPN mandates.While it is not a big deal, I frequently like to tweak what hosts are going to the
openconnect
VPN connection, and what goes directly to my default route. I span a custom configuration file to do this, which gets passed to thevpn-slice
parameters whenever I execute my VPN script. However, authenticating with the VPN unfortunately requires 2FA in my case, so restarting it is not convenient.It would be great if I could start the
openconnect
VPN tunnel, then spawn a separate process forvpn-slice
that sets up the routes, so I can reload thatvpn-slice
instance whenever I like and have my routing configuration updated. This would all be transparent to the VPN connection, which would keep running happily in the background.How hard is this? Is it already possible with some hacks? It may be out of scope for
vpn-slice
, and I understand if this is the case. Maybe a project could wrap and daemonizevpn-slice
to produce the desired behaviour?p.s. if you add some donation link to the project's README, I would love to buy you a coffee for your work. :)
Thanks
The text was updated successfully, but these errors were encountered: