User Profile: stringer
Forum Replies Created
-
AuthorPosts
-
stringer
ParticipantIs pcWRT susceptible to the KRACK vulnerability? If so, what is the plan for patching this at the router layer? Thanks!
ParticipantOK! Looks like that did it. After adding that line to the host list, I’ve cycled Parental Controls, waited several seconds, restarted the browser, and google continues to work. I’ve also checked another computer that has CovEyes installed, and it’s working there as well (we have three Macs with C/E installed on our network). Should I leave the
216.239.32.20 forcesafesearch.google.comline in the host list? Thanks so much for the help! I really wanted to make this work.ParticipantEven flushing DNS now isn’t working. I’ve re-started the browser, rebooted the laptop, flushed DNS, and google still won’t work while Parental Controls are ON (I haven’t cycled it during this phase of troubleshooting).
ParticipantOK. Checked Safe search ON. Re-ran nslookup and ping:
ScottsLaptop:~ Scott$ nslookup www.google.com Server: 192.168.10.1 Address: 192.168.10.1#53 Non-authoritative answer: www.google.com canonical name = forcesafesearch.google.com. Name: forcesafesearch.google.com Address: 216.239.32.20 ScottsLaptop:~ Scott$ ping www.google.com PING www.google.com (216.239.32.20): 56 data bytes 64 bytes from 216.239.32.20: icmp_seq=0 ttl=53 time=25.206 ms 64 bytes from 216.239.32.20: icmp_seq=1 ttl=53 time=504.421 ms 64 bytes from 216.239.32.20: icmp_seq=2 ttl=53 time=529.527 ms 64 bytes from 216.239.32.20: icmp_seq=3 ttl=53 time=143.068 ms 64 bytes from 216.239.32.20: icmp_seq=4 ttl=53 time=473.354 ms 64 bytes from 216.239.32.20: icmp_seq=5 ttl=53 time=38.070 ms ^C --- www.google.com ping statistics --- 6 packets transmitted, 6 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 25.206/285.608/529.527/220.615 msThere was a brief delay between executing the nslookup and getting a response (maybe 3-4 sec). Google still wasn’t working. With Parental Controls still on, re-ran:
sudo killall -HUP mDNSResponderGoogle then worked, with Parental Controls still enabled.
Re-ran nslookup and ping, for comparison:
ScottsLaptop:~ Scott$ nslookup www.google.com Server: 192.168.10.1 Address: 192.168.10.1#53 Non-authoritative answer: www.google.com canonical name = forcesafesearch.google.com. Name: forcesafesearch.google.com Address: 216.239.32.20 ScottsLaptop:~ Scott$ ping www.google.com PING www.google.com (216.239.32.20): 56 data bytes 64 bytes from 216.239.32.20: icmp_seq=0 ttl=53 time=49.380 ms 64 bytes from 216.239.32.20: icmp_seq=1 ttl=53 time=48.388 ms 64 bytes from 216.239.32.20: icmp_seq=2 ttl=53 time=35.262 ms 64 bytes from 216.239.32.20: icmp_seq=3 ttl=53 time=46.949 ms 64 bytes from 216.239.32.20: icmp_seq=4 ttl=53 time=35.086 ms 64 bytes from 216.239.32.20: icmp_seq=5 ttl=53 time=36.487 ms ^C --- www.google.com ping statistics --- 6 packets transmitted, 6 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 35.086/41.925/49.380/6.368 msThen I cycled Parental Controls (OFF then ON). Google stopped working. Re-ran
sudo killall -HUP mDNSResponder
but Google still isn’t working. Re-started the browser as well, but no luck.I don’t think I’ll need to re-cycle Parental Controls often, so perhaps resetting the DNS cache once in a while isn’t an unacceptable workaround. Mobile devices seem to still be working.
ParticipantYes, safe search is unchecked.
ParticipantAnd sure enough, after cycling Parental Controls off then on, google no longer works again. I have to wipe the DNS cache to restore google access every time Parental Controls is turned on.
ParticipantRe-ran nslookup and ping:
ScottsLaptop:~ Scott$ nslookup www.google.com Server: 192.168.10.1 Address: 192.168.10.1#53 Non-authoritative answer: Name: www.google.com Address: 198.52.15.215 Name: www.google.com Address: 198.52.15.230 Name: www.google.com Address: 198.52.15.226 Name: www.google.com Address: 198.52.15.219 Name: www.google.com Address: 198.52.15.207 Name: www.google.com Address: 198.52.15.222 Name: www.google.com Address: 198.52.15.241 Name: www.google.com Address: 198.52.15.236 Name: www.google.com Address: 198.52.15.249 Name: www.google.com Address: 198.52.15.234 Name: www.google.com Address: 198.52.15.237 Name: www.google.com Address: 198.52.15.221 Name: www.google.com Address: 198.52.15.251 Name: www.google.com Address: 198.52.15.211 Name: www.google.com Address: 198.52.15.245 ScottsLaptop:~ Scott$ ping www.google.com PING www.google.com (216.239.32.20): 56 data bytes 64 bytes from 216.239.32.20: icmp_seq=0 ttl=53 time=16.421 ms 64 bytes from 216.239.32.20: icmp_seq=1 ttl=53 time=14.211 ms 64 bytes from 216.239.32.20: icmp_seq=2 ttl=53 time=14.148 ms 64 bytes from 216.239.32.20: icmp_seq=3 ttl=53 time=15.839 ms 64 bytes from 216.239.32.20: icmp_seq=4 ttl=53 time=20.862 ms 64 bytes from 216.239.32.20: icmp_seq=5 ttl=53 time=13.230 ms ^C --- www.google.com ping statistics --- 6 packets transmitted, 6 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 13.230/15.785/20.862/2.512 msAlso ran
sudo killall -HUP mDNSResponderto reset the DNS cache. Google is now working. I reset the cache when I first had this problem, and that fixed google for a little bit, but then it stopped working again after cycling Parental Controls. After cycling Parental Controls, re-ran nslookup and ping again:ScottsLaptop:~ Scott$ nslookup www.google.com Server: 192.168.10.1 Address: 192.168.10.1#53 Non-authoritative answer: Name: www.google.com Address: 198.52.15.236 Name: www.google.com Address: 198.52.15.226 Name: www.google.com Address: 198.52.15.241 Name: www.google.com Address: 198.52.15.215 Name: www.google.com Address: 198.52.15.207 Name: www.google.com Address: 198.52.15.237 Name: www.google.com Address: 198.52.15.211 Name: www.google.com Address: 198.52.15.219 Name: www.google.com Address: 198.52.15.249 Name: www.google.com Address: 198.52.15.222 Name: www.google.com Address: 198.52.15.245 Name: www.google.com Address: 198.52.15.251 Name: www.google.com Address: 198.52.15.221 Name: www.google.com Address: 198.52.15.234 Name: www.google.com Address: 198.52.15.230 ScottsLaptop:~ Scott$ ping www.google.com PING www.google.com (216.239.32.20): 56 data bytes 64 bytes from 216.239.32.20: icmp_seq=0 ttl=53 time=13.653 ms 64 bytes from 216.239.32.20: icmp_seq=1 ttl=53 time=15.773 ms 64 bytes from 216.239.32.20: icmp_seq=2 ttl=53 time=16.307 ms 64 bytes from 216.239.32.20: icmp_seq=3 ttl=53 time=18.937 ms 64 bytes from 216.239.32.20: icmp_seq=4 ttl=53 time=16.303 ms 64 bytes from 216.239.32.20: icmp_seq=5 ttl=53 time=13.874 ms 64 bytes from 216.239.32.20: icmp_seq=6 ttl=53 time=22.618 ms ^C --- www.google.com ping statistics --- 7 packets transmitted, 7 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 13.653/16.781/22.618/2.889 msParticipantOne question the CovEyes tech asked was whether the router could exclude executable files. He was oriented toward the windows OS, though, and couldn’t identify the applicable executable for CovEyes on a Mac. From my own looking around, it looks like it would be:
/Applications/Covenant Eyes.app/Contents/MacOS/Covenant EyesHe also mentioned that the Mac domains are:
mac.ces.cvnt.netandapi.cvnt.netNot sure if that’s helpful.
ParticipantThanks. I figured it was a conflict. Layered filtering systems tend to not play well together. I tried the host name, but it didn’t help. I’ve also turned off the SafeSearch option in the Parental Controls pane, but that doesn’t seem to make a difference, either. The only way I’ve been able to get google search to work is to disable all Parental Controls, which essentially makes this router useless (or no better than any other router anyway) for me. I’m hoping to find a solution, otherwise, I’ll need to return the router. Thanks for the continuing support. I’ve also contacted Covenant Eyes, but they’re not familiar with your router nor have they had any previous reports of conflicts.
ParticipantI do have Covenant Eyes running on my laptop.
nslookup produced the following result:
ScottsLaptop:~ Scott$ nslookup www.google.com
Server: 192.168.10.1
Address: 192.168.10.1#53Non-authoritative answer:
www.google.com canonical name = forcesafesearch.google.com.
Name: forcesafesearch.google.com
Address: 216.239.38.120ping produced the following result:
ScottsLaptop:~ Scott$ ping www.google.com
PING www.google.com (216.239.32.20): 56 data bytes
64 bytes from 216.239.32.20: icmp_seq=0 ttl=53 time=35.676 ms
64 bytes from 216.239.32.20: icmp_seq=1 ttl=53 time=16.463 ms
64 bytes from 216.239.32.20: icmp_seq=2 ttl=53 time=18.524 ms
64 bytes from 216.239.32.20: icmp_seq=3 ttl=53 time=14.238 ms
[…. several other lines ….]
64 bytes from 216.239.32.20: icmp_seq=76 ttl=53 time=13.554 ms
64 bytes from 216.239.32.20: icmp_seq=77 ttl=53 time=14.907 ms
^C
— www.google.com ping statistics —
78 packets transmitted, 78 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 11.933/27.036/495.013/59.158 msParticipantHere’s a screen grab of the error:
(“The requested URL is blocked on this network.
http://www.google.com:443”)-
This reply was modified 7 years, 11 months ago by
stringer.
-
This reply was modified 7 years, 11 months ago by
-
AuthorPosts
