I've recently installed Gargoyle 1.3.9 on my WRTG version 1.1.
I was trying to make the Access Restrictions work, and was having trouble. I would add a rule like this:
Uncheck All Network Access.
Click on WebSite URLs and click Block Only.
Full URL contains "nitrome"
Click on the Add New Rule button
Click on the Save Changes button at the bottom of the page.
Then if I start a new browser and try to go to nitrome.com, it still lets me go to the page.
However, I discovered that if I now go to the Connection - Basic page and press the Save Settings button at the bottom of the page, now all my Access Restrictions start working!
Why doesn't the Save Settings on the Access Restrictions page cause the restriction rules to start working in the router? At least I have a workaround.
Access Restrictions don't stick workaround
Moderator: Moderators
Re: Access Restrictions don't stick workaround
As as been previously documented here there is a bug in v1.3.9 which causes access restrictions not to take affect until the restriction is saved and the router is rebooted.
This issue has been resolved in the GIT but a new Gargoyle revision has not yet released.
Now I have not had a chance to read and understand all the issues/complaints that I have seen on this subject. So its possible that some other problem exists as well. In the spirit of open source firmware it would be really cool is someone who is having issues like this would build a new image from the GIT and try it to see if it resolved their problems or not.
Then I would feel much better that we have this problem fixed.
This issue has been resolved in the GIT but a new Gargoyle revision has not yet released.
Now I have not had a chance to read and understand all the issues/complaints that I have seen on this subject. So its possible that some other problem exists as well. In the spirit of open source firmware it would be really cool is someone who is having issues like this would build a new image from the GIT and try it to see if it resolved their problems or not.
Then I would feel much better that we have this problem fixed.
Linksys WRT1900ACv2
Netgear WNDR3700v2
TP Link 1043ND v3
TP-Link TL-WDR3600 v1
Buffalo WZR-HP-G300NH2
WRT54G-TM
Netgear WNDR3700v2
TP Link 1043ND v3
TP-Link TL-WDR3600 v1
Buffalo WZR-HP-G300NH2
WRT54G-TM