| Age | Commit message (Collapse) | Author |
|---|
|
The IS_${platform} constants are used in more places than the vpn
module. Let's define them in leap.bitmask.
|
|
|
|
for now, we'll be hardcoding tcp as a more reliable alternative, no
matter what the provider announces.
explicitely specifying ipv4 should fix the case in which vpn fails to
start because ipv6 is disabled.
-Resolves: #9181, #9129
|
|
- Resolves: #9099
|
|
|
|
|
|
Don't persist-tun on the vpn, so it can restart properly. Also let's
match better the options that are sent and taken into account from
bitmask-root.
- Resolves: #9048
|
|
|
|
This is a first approach to automatic gateways selection.
More things are missing:
- allow manual selection, by location or country code.
- take the hemisphere into account.
- expose the selected gw to the api/cli
but overall seems this is a good approach to make 0.10 release usable in
terms of vpn.
- Resolves: #8804
|
|
Some reordering, and general cleanup of options.
Some of the openvpn options are added now by bitmask-root.
- Resolves: #8948
|
|
with these fixes, I'm able to finally launch openvpn and firewall on
osx. :)
all that's left for a minimum vpn release is packaging and installing
all the helpers in the proper place.
|
|
|
|
no need to setup LD_LIBRARY_PATH anymore, we're shipping a static
binary.
|
|
I changed most of the logger statements to use a class attribute, in
this way it's easier to identify which class it's logging them.
in some cases I leave a module-level logger, when we're either using
functions or when the module it's too small.
at the same time I did a general review and cleanup of the logging
statements.
|
|
Instead of hardcoding them in the code.
|
|
|
|
|
|
|
|
|
|
non functional at the moment, but started doing some cleanup
|
