How can I bypacc netgear live parental control from my NAS
I have a NetGear router with opendns live parental control that works fine.
I have also a little nas with http, bittorrent, ... download feature. The Genie application can't run on the nas! How can I bypass the parental control for it?
It is not foreseen to bypass LPC with anything other than an LPC bypass account. Whatever, I can see the following options:
- Configure LPC more granular, i.e. select "Custom" and block only the categories you want to block and exempt the categories of domains being needed by the NAS, e.g. P2P/File sharing.
- Add the domains being blocked to the local hosts file on the NAS.
- If your NAS is Windows based, you can try the user utility from https://www.opendns.com/downloads/
- Do not use LPC but the normal OpenDNS Home instead. You can then configure different non-OpenDNS server addresses on the NAS.
1 - I can avoid using live parental control and just put different dns to different pc, tablet, phones, nas, etc... - I prefer a centralized system.
2 - I can put a different dns in NAS - but it won't works because the router, working in live parentale, catch every dns request and turn them to opendns
3 - the nas is a linux based nas and genie won't work
4 - Adding the domain blocked to /etc/hosts is not simple, think about torrent files... sites changes everytime
- This is in principle the last item I proposed. It is centralized on the router but with your NAS as the only exception. You do not need to configure different DNS on each device.
- Yes, I know. Therefore this was not something I proposed.
- Ok. This is what I thought.
- Nothing is simple if you want to circumvent LPC which is not foreseen to be circumvented. Else it would be counterproductive, not doing what one expects it to do efficiently.
So after all, you'll want to go for my past proposal:
Do not use LPC but the normal OpenDNS Home instead. You can then configure different non-OpenDNS server addresses on the NAS.
This is your centralized system with the NAS as the only exception.
I agree. I can put opedns servers in dhcp/dns settings so every pc will have it. If I have a pc or the NAS I want to be outside control I have only to change its dns.
It works. To be sure at 100% I can use, for example 18.104.22.168 and 22.214.171.124 dns and allow outgoing traffic on that destinations only for the pc I want to be outside control :-)
in a way that if someone try to change its dns it won't work. More! I can stop traffic on port 53 rather than the privileged pc (mac addresses or ip)
"I can put opedns servers in dhcp/dns settings so every pc will have it."
This is the less preferred method. You better configure the WAN side of the router with the OpenDNS resolver addresses:
If you configure the DHCP side, then your devices may face troubles with internal name resolution. Examples would be that http://routerlogin.net/ and devices like network printers, NASes, etc. don't work anymore. It is better to point the devices' DNS to the router. Then "every pc will have it" too, i.e. will use OpenDNS through the router.
"If I have a pc or the NAS I want to be outside control I have only to change its dns."
This is correct. It points to this DNS service then instead of to the router (which again points to OpenDNS).
Another thing in this context: you now have to use and to configure the dashboard at https://dashboard.opendns.com/settings/ and your dashboard at https://netgear.opendns.com/ is irrelevant now with LPC disabled. And you must run an Updater to keep your IP address information updated at OpenDNS, else your settings and collecting stats do not take effect.
Please sign in to leave a comment.