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

Whitelist of wifi networks #27

Closed
joel-porquet opened this issue Oct 26, 2017 · 3 comments · May be fixed by #1418
Closed

Whitelist of wifi networks #27

joel-porquet opened this issue Oct 26, 2017 · 3 comments · May be fixed by #1418
Labels
2. to review enhancement enhancement of a already implemented feature/code feature: 🔄 sync engine

Comments

@joel-porquet
Copy link

It'd be great to be able to define a list of wifi networks for which the client is authorized to perform synchronization. It happens sometimes that I tether my phone to my laptop through wifi and I'd prefer not to have big data transfer from nextcloud during that time. From now, I manually pause the synchronization but ideally it'd be very convenient to just define which wifi networks are OK for sync (this way, all other wifi networks - such as in airports, coffee shops, etc.- would be deactivated by default).
Thanks!

@michaelstingl
Copy link
Contributor

There is very affordable existing software out there that blocks traffic on tethered connections: https://www.tripmode.ch/

Related upstream issue: owncloud/client#4808

@HammyHavoc
Copy link

Would be interesting for file sync with local servers if it was dictated by network.

@Rello
Copy link
Contributor

Rello commented Nov 1, 2024

Hello,
I am closing this because it is not on the roadmap due to prioritization.

@Rello Rello closed this as not planned Won't fix, can't repro, duplicate, stale Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2. to review enhancement enhancement of a already implemented feature/code feature: 🔄 sync engine
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants