Diversion Multiple Whitelists in Diversion

[PeterLiljedahl]

As Diversion currently works we can add a secondary blocklist (preferrable smaller) and link it to an IP on the LAN.
I am thinking if it's possible to instead have one large main blocklist as usual for all devices and then use separate whitelists
for a couple of IP's on the network?.
Would this require a separate instance of dnsmasq started for every IP we want to associate to a whitelist?
Would it bog down the CPU if we were to run lets say a medium blocklist with 3 whitelists (3 IP's) with 5 domains in each?

 

[SomeWhereOverTheRainBow]

As Diversion currently works we can add a secondary blocklist (preferrable smaller) and link it to an IP on the LAN.
I am thinking if it's possible to instead have one large main blocklist as usual for all devices and then use separate whitelists
for a couple of IP's on the network?.
Would this require a separate instance of dnsmasq started for every IP we want to associate to a whitelist?
Would it bog down the CPU if we were to run lets say a medium blocklist with 3 whitelists (3 IP's) with 5 domains in each?

You could try this out, I think it does what you are trying to do.

GitHub - SidShetye/guiderails: Guiderails is a wrapper to DNSMASQ that blacklists everything and then selectively whitelists specific servers for a fully controlled and curated internet experience.

Guiderails is a wrapper to DNSMASQ that blacklists everything and then selectively whitelists specific servers for a fully controlled and curated internet experience. - SidShetye/guiderails

github.com

 

[PeterLiljedahl]

Thanks man, I wonder if this could run alongside diversion given it wraps around dnsmasq which Diversion also uses
creating race conditions, status conflicts etc.
Guiderails might be perfect for iot devices and cams and alike.

 

[thelonelycoder]

Thanks man, I wonder if this could run alongside diversion given it wraps around dnsmasq which Diversion also uses
creating race conditions, status conflicts etc.
Guiderails might be perfect for iot devices and cams and alike.

I believe it is best if Diversion had such an option. Let me see what I can do.

 

[PeterLiljedahl]

Thanks man, will be interesting to see how it turns out.

 

[thelonelycoder]

Thanks man, will be interesting to see how it turns out.

I was hoping to work on this feature last weekend. A pressing work related matter had me travel to the US on short notice, figure out the reason for the failure and get it back to working order. I returned yesterday and today another system refuses to work. So this too needs my personal attention which I have to go to this Saturday. Luckily, it‘s only 2 hours away from where I live but my weekend is probably shot again.
The joy of being the senior troubleshooter has no bounds

So be patient, I‘ll get to coding as soon as I can.

 

[SomeWhereOverTheRainBow]

I was hoping to work on this feature last weekend. A pressing work related matter had me travel to the US on short notice, figure out the reason for the failure and get it back to working order. I returned yesterday and today another system refuses to work. So this too needs my personal attention which I have to go to this Saturday. Luckily, it‘s only 2 hours away from where I live but my weekend is probably shot again.
The joy of being the senior troubleshooter has no bounds

So be patient, I‘ll get to coding as soon as I can.

We humbly await your workings kind sir! Hope everything is well.

 

[jrichard326]

Thank you for all of your hard work. I am also interested in this, except I would be looking to add a secondary blacklist.

 

[thelonelycoder]

@PeterLiljedahl and others interested in this threads feature request.

As I understand the OP's post and the linked guiderails wrapper script (https://github.com/SidShetye/guiderails) suggest that this feature be a restricted access for specific devices connected to the router.

I implemented a solution into Diversion called "Restricted access for devices" that DENIES all domains except those specifically ALLOWED in a whitelist, exactly as guiderails does.
Is this how the OP wants it and is there indeed interest for such a feature?
If so, I'll clean and polish the code and ship it with the next Diversion update.

 

[SomeWhereOverTheRainBow]

@PeterLiljedahl and others interested in this threads feature request.

As I understand the OP's post and the linked guiderails wrapper script (https://github.com/SidShetye/guiderails) suggest that this feature be a restricted access for specific devices connected to the router.

I implemented a solution into Diversion called "Restricted access for devices" that DENIES all domains except those specifically ALLOWED in a whitelist, exactly as guiderails does.
Is this how the OP wants it and is there indeed interest for such a feature?
If so, I'll clean and polish the code and ship it with the next Diversion update.

Nice work @thelonelycoder . This indeed is a great option to have. Especially if it can be used with either primary or secondary blocking features. I could easily see one segment of the network being blocked, and another segment of the network simply being filtered. Great work.

 

[PeterLiljedahl]

Thanks for your efforts and talking a little about comming ideas.
I didnt install and test guiderails because I really dont know how to do these linux installations
but diversion is more familiar.
It will be exciting to test these things out.