Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Network Whitelist For Vorta on Linux #355

Closed
GuardedAirplane opened this issue Aug 31, 2019 · 4 comments
Closed

Network Whitelist For Vorta on Linux #355

GuardedAirplane opened this issue Aug 31, 2019 · 4 comments
Labels
help wanted This issue is available, comment if you want to fix it status:planning For large features, plan it out before implementation type:feature New functionality

Comments

@GuardedAirplane
Copy link

Currently there is no way to prevent Vorta from backing up automatically on certain networks. On my Mac, I use this feature to prevent backing up on my hotspot and my dad's satellite internet connection. My linux laptop does not have this feature, and I accidentally ate up 75% of my hotspot allowance because of it.

Implementing a Networks tab such as the one found on macOS. Looking at a past issue, it looked like getting previous networks was not supported, so perhaps allowing a manual input of SSIDs or router MAC addresses could work.

An alternative solution, might be a location based solution could be used. As in, if you are at your home address, backup, if not, don't.

@m3nu
Copy link
Contributor

m3nu commented Sep 1, 2019

Yeah. Would be nice to have this for Linux. Current blocker is that I don’t know of a universal way to get a list of past Wi-Fis and the current Wi-Fi.

With this info the feature could be implemented rather easily.

@m3nu m3nu added help wanted This issue is available, comment if you want to fix it type:feature New functionality labels Sep 1, 2019
@GuardedAirplane
Copy link
Author

Would executing '$ iwgetid' in the background every so often or right before a backup operation work? That gives the current SSID, and you could store any newly observed ones in a log file to be added to the list in the GUI.

@Vinno97
Copy link

Vinno97 commented Sep 12, 2019

I think a more robust way would be to listen for D-Bus messages sent by that get sent when an interface change occurs. That way there is no need for polling and makes sure Vorta gets notified immediately.


Gists like this and this one show the basic principle.

@m3nu m3nu added the status:planning For large features, plan it out before implementation label May 29, 2020
@samuel-w
Copy link
Contributor

samuel-w commented Sep 3, 2020

I think this is closed by #547

@m3nu m3nu closed this as completed Sep 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted This issue is available, comment if you want to fix it status:planning For large features, plan it out before implementation type:feature New functionality
Projects
None yet
Development

No branches or pull requests

4 participants