summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorRuben Pollan <meskio@sindominio.net>2018-01-08 18:01:07 +0100
committerRuben Pollan <meskio@sindominio.net>2018-01-08 20:06:34 +0100
commit776447a9c03d969928b8fb124738969ebf265ca0 (patch)
tree6361497f6dc0d9bdb051ef0083dddf9c87b421c6 /docs
parentad55e80771ed0f1308a60c6acaabbc57b0a8f49d (diff)
[feat] try other gateways if the main one fails
Removing '--persist-ip' param on openvpn it will try to connect to a different gateway if the first one fails. This means, that in case of network disconnection for some minutes bitmask will keep rotating between the different gateways and one the network comes back it will not connect anymore to the first one, but to the one that was trying at this moment. - Resolves: #9188
Diffstat (limited to 'docs')
-rw-r--r--docs/changelog.rst1
-rw-r--r--docs/vpn/index.rst19
2 files changed, 20 insertions, 0 deletions
diff --git a/docs/changelog.rst b/docs/changelog.rst
index aa7ac132..975cc9a1 100644
--- a/docs/changelog.rst
+++ b/docs/changelog.rst
@@ -10,6 +10,7 @@ Features
- `#8217 <https://0xacab.org/leap/bitmask-dev/issues/8217>`_: renew OpenPGP keys before they expire.
- `#9074 <https://0xacab.org/leap/bitmask-dev/issues/9074>`_: pin provider ca certs.
- `#6914 <https://0xacab.org/leap/bitmask-dev/issues/6914>`_: expose an API to retrive message status.
+- `#9188 <https://0xacab.org/leap/bitmask-dev/issues/9188>`_: try other gateways if the main one fails.
- Set a windows title, so that Bitmask windows can be programmatically manipulated.
Bugfixes
diff --git a/docs/vpn/index.rst b/docs/vpn/index.rst
index e5549895..95eb08c2 100644
--- a/docs/vpn/index.rst
+++ b/docs/vpn/index.rst
@@ -38,6 +38,25 @@ You can list all the configured locations using the CLI::
This manual override functionality will be exposed through the UI and the CLI in release ``0.11``.
+Gateway failures
+-----------------------------------
+
+If Bitmask VPN fails to connect to one gateway it will try with the next
+following gateway selection order.
+
+In case of connection loss Bitmask will keep trying to connect to each of the
+gateways again and again until the connection comes back. When the connection
+is back Bitmask will connect to the gateway that was trying at the moment.
+In practice after a reconnection the gateway that Bitmask gets connected is
+practically random.
+
+Turning the VPN down and up again after a reconnection ensures that Bitmask
+will try again the first gateway.
+
+In the future Bitmask should become more in control of the reconnect process,
+that currently is handled by openvpn, and detect reconnections to select the
+gateways better.
+
Autostart
---------
Autostart is not implemented yet in the 0.10 versions of Bitmask, but you can probably use