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

Make specific lists/entries only apply to external/internal IPs to save mobile data caps #1096

Open
3 tasks done
DandelionSprout opened this issue Oct 20, 2019 · 1 comment

Comments

@DandelionSprout
Copy link
Member

DandelionSprout commented Oct 20, 2019

Related to #1081, but with a pretty different aim:

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

  • I am running the latest version (0.99.0)
  • I checked the documentation and found no answer
  • I checked to make sure that this issue has not already been filed

Problem Description

Imagine this theorethical scenario: You're a Nintendo Switch player who likes to bring it along for bus rides and such. One day you head into a store to buy a new AAA game for it, with the intention of playing it on the bus on the way home. So you've got on the bus, connected the Switch to the internet through Android signal tethering, and are getting ready to play.

The very last thing you and your mobile data subscriptions would want to occur then, is a ~25GB update patch for the game.

If it was possible to make that certain lists and/or entries only applied to external (essentially non-192.168.*.*) or internal (192.168.*.*) IPs, it could become possible to use update-blocking filterlists (e.g. https://raw.githubusercontent.com/Akamaru/Pi-Hole-Lists/master/nintendoblock.txt) while being out in public, while not using such lists at home so that players can download updates that are necessary to e.g. be able to play games online, without needing to fear data caps.

If thought about broadly, this would also allow AdGuard Home to advertise with being able to salvage peoples' mobile data caps.

Proposed Solution

If applied to lists, this'd require some brand new settings in the Filters menu. If applied to entries, I imagine something like ||digibutter.nerr$external and ||digibutter.nerr$internal.

Alternatives Considered

None at the time of writing.

Additional Information

I do not currently own a Switch, and thus cannot first-hand confirm the scenario's relevance, but I do plan to buy one within the next 1-4 weeks.

All of this would most probably also apply to Steam/Origin laptop players and PlayStation Vita players. Maybe even to people who fear Windows 10 feature updates or major Office 365 updates on the go.

@ghost
Copy link

ghost commented Oct 20, 2019

Proposed Solution ✌️

Alternatives Considered

I think i like it. as per my understand about your explanation, we may need to have an option in 'Clients' area (or maybe Filters area) for set 'Allowed networks'(or disallowed/whitelisted) ex: 192.168.1.0/24, 172.16.0.0/16 for each then the specific filter will not apply when connect to them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants