The old client would remember that you had the VPN running so when you started it again it would immediately start the VPN. The new client will start the UI, but the VPN wont start, unless you press the button to start it. It should either start automatically, or remember the last state and reproduce it.
Designs
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
you're right, we need to port the autostart feature with the newest packages/bundles.
I'm wondering if we should try to go for systemd integration and have a dedicated bitmaskd process to launch this as soon as possible during the boot process, instead of keep doing the 'autostart when user launches the ui'.
A user on #leap came by asking about this, noting that they can get bitmask to start on boot, but starting the VPN requires manually pressing of the button.
About @kali's question - I like the idea of systemd, but I suspect there are people who will not want things to start on boot as well as people who do, so whatever path is taken it should not lock users into one particular state.
Imo we should first enable the option to auto-connect on bitmask startup. This looks easy to accomplish and helps a lot.
Getting VPN up and running as early as possible on boot also seems a good idea but this is going to be a lot more work to do right, and then there are dozens of distribution which their different boot schemas.
I'd say we should not focus on this now but maybe later.
Hey folks, came here to ask about this and then realised this is a Python project! Perhaps I can submit a patch! Where would I go looking for making a start on this ticket? It appears that the direction is not clear yet. I'd love to have bitmask auto-connecting on boot.
Hey folks, came here to ask about this and then realised this is a Python
project! Perhaps I can submit a patch! Where would I go looking for making a
start on this ticket? It appears that the direction is not clear yet. I'd love
to have bitmask auto-connecting on boot.
right now, latest master implements the desktop entry for autostart (as long as
you switch down bitmask with vpn on).
I think we could go for a systemd (or other alternatives) scripts, maybe reading
a config file in /etc/bitmaskd.conf so that we can configure which user bitmask
should be running as.