Run applications through VPN tunnels with temporary network namespaces
Changelog:
interface
argument from vopono config file ~/.config/vopono/config.toml
- issue #254 PR #258vopono.host
entry to the hosts file in the network namespace with the $VOPONO_HOST_IP
if --allow-host-access
is used. This allows you to access services on the host at http://vopono.host:80
etc. from inside the network namespace. Addresses issue #262 PR #264$VOPONO_FORWARDED_PORT
environment variable if --port-forwarding
or --custom-port-forwarding
are used for
provider port forwarding. Addresses issue #260 PR #264Changelog:
--custom-port-forwarding {protonvpn,pia}
flag to indicate which provider's implementation to use for custom config files. Fixes issue #247--port-forwarding-callback
script support to ProtonVPN port forwarding too (the port number is provided to the script as the first argument $1
).~
can be used in custom config arguments).application
to be specified in vopono config.toml
filemacro_rules!
macros (could still be improved with a procedural macro for getting fields automatically).--verbose
Changelog:
--create-netns-only
argument for use with firejail - PR #242Changelog:
--protonvpn-port-forwarding
argument - PR #240 , part of issue #226 , note servers must support it and, if using OpenVPN, +pmp
must be appended to the OpenVPN username (in ~/.config/vopono/proton/openvpn/auth.txt
)Changelog:
Changelog:
Changelog:
vopono servers
listing is now sortedNote that issue #181 is still pending.
Changelog:
wireguard_preup
method - issue #186 , PR #187Changelog:
Changelog:
--allow-host-access
flag to allow accessing ports on the localhost (usually via the IP address 10.200.1.1
) - #159--custom-netns-name
to override the network namespace name generation, as part of issue #131~/.config/vopono/logs/
to fix #152Main PR: #178
Note for the .deb files - armhf is armv7, armel is armv5 and arm64 is aarch64 / armv8