safeguard

[#1]

I'm not going to talk about how to bypass Safeguard for obvious reasons, but the DNS needs setting to Auto.

[#2]

In which case - and I am sorry to be unkind - but that makes Safeguard about as much use as a chocolate fireguard in stopping children accessing things they shouldn't

[#3]

It would appear that's the case Jim, I'm still investigating. It would appear that a "Reboot" as specified in the "instructions" is required because the (modem/)router need to pick up the new DNS which of course hasn't been mentioned.
The only reason I discovered this was because of another mention of Safeguard elsewhere caused me to check whether anything had been changed as a result of previous criticism about the general "reboot" instruction that gets bandied about far too frequently. I decided to use the Live Chat to see if I could find out why and got a response about it needing to pick up the correct DNS servers. I stated that the reboot issue had been mentioned here on the forum and got the response
Ok, If you've already raised this on the forum then the relevant team will look into it.
Clearly the relevant team have NOT looked into it as no explanation has been forthcoming here nor any additional explanation added to the guidance and help pages for Safeguard. Not good enough Plusnet 

[#4]

I haven't checked but I very much doubt that a reboot of a 2704n would override the DNS setting if they aren't set to automatic unless the TR069 system is going to set them back to automatic

[#5]

A reboot wouldn't involve the use of TR-069 IIRC, only a Reset
Reboots don't remove the User's username and password.

[#6]

I know that but what I don't know is whether it can selectively change the DNS settings if so instructed

[#7]

Is it possible to configure the firewall to block all requests on port 53 and, if so, would that force the use of the router's DNS?

[#8]

I wouldn't have thought so, as it's too locked down. Limited choices can be seen in the attached.

[#9]

Any security system which is not open about how it works, is a bad choice.
Never trust an ISP to do your work for you if you want to ensure that your internet connection only allows permitted sites.

[#10]

Does it block a site if you go to it's IP address.....?

[#11]

St3 may be able to answer that as he has it running, but my guess would be yes it would if it's DNS based (most of these are - eg. OpenDNS) because if you don't use DNS, DNS can't block it. But don't forget that won't be the case for any that are blocked as a result of being on the IWF list as they are blocked differently by ISPs.

[#12]

yep

[#13]

Having just re-read my previous reply, I realise it's as clear as mud    but because of the daft 24hr edit rule I can't make it clearer.
I was responding to

Quote from: Lorian

Does it block a site if you go to it's IP address.....?

The answer to which should be No, not yes.The post should have read -

Quote

St3 may be able to answer that as he has it running, but my guess would be no, if it's DNS based (most of these are - eg. OpenDNS) because if you don't use DNS (ie use an IP address), DNS can't block it. But don't forget that won't be the case for any that are blocked as a result of being on the IWF list as they are blocked differently by ISPs.

[#14]

Quote from: Chris

I'm not going to talk about how to bypass Safeguard for obvious reasons, but the DNS needs setting to Auto.

Hi Chris,
PlusNet are in the predicted "Rock and a hard place" syndrome.  A level of parental control has been implemented, but how it works cannot be explained as in doing so informs how to hack around it.  Conversely it equally does not inform what else might be needed (within the home network) to inhibit hack-around.
This is not the simple space many have advocated it is / should be.  In the absence of parental supervision of children's internet activity, protection through technology requires more skill than many with years of general IT experience have.  As implied by OJ, to truly lock down access, inhibition of reconfiguring client platforms is an essential part of the solution.
Kevin

[#15]

An easier solution was suggested, blocking all port 53 requests from connected devices. But the router has to have that capability, I'm not sure where to start on that one, need to investigate, with the 2704n that wouldn't be possible, that's for sure.
There's a couple of Router experts that may know how to go about it if it's possible, hopefully they'll come and post.