Restriction exceptions not working
Moderator: Moderators
Restriction exceptions not working
I'm running 1.9.x and thought all was doing as expceted, then realised my restrictions weren't working.
If I select
Firewall->Restrictions-New Restriction Rule
and select All, then activate the rule, that works fine - no devices have access.
If I then edit, change All Hosts to All Hosts except x.x.x.x then enter and save ANY IP address, it enables ALL devices on the network, not just the one that was intended.
Is this a known issue or something that is a WIP?
A similar thing seems to happen when I select a time range rather than 'All Day. Every Day'
Cheers
If I select
Firewall->Restrictions-New Restriction Rule
and select All, then activate the rule, that works fine - no devices have access.
If I then edit, change All Hosts to All Hosts except x.x.x.x then enter and save ANY IP address, it enables ALL devices on the network, not just the one that was intended.
Is this a known issue or something that is a WIP?
A similar thing seems to happen when I select a time range rather than 'All Day. Every Day'
Cheers
Re: Restriction exceptions not working
screen shots please
Re: Restriction exceptions not working
This works and stops everything from having access.
http://i1088.photobucket.com/albums/i32 ... ih1xwa.png
This results in ALL devices to be excepted and therefore have access (instead of just the one specified).
http://i1088.photobucket.com/albums/i32 ... 22qffz.png
http://i1088.photobucket.com/albums/i32 ... ih1xwa.png
This results in ALL devices to be excepted and therefore have access (instead of just the one specified).
http://i1088.photobucket.com/albums/i32 ... 22qffz.png
Re: Restriction exceptions not working
In my opinion 75% of problems with gargoyle are a broken config.
You could first try "fail-safe reset" or re-flash a new fresh install than try again.
Don't use any backup files or preserver settings when re-configuring.
Recommend the lasted stable firmware
viewtopic.php?f=14&t=11036
Just because of where it is in the development cycle this this is the most stable build ever.
You could first try "fail-safe reset" or re-flash a new fresh install than try again.
Don't use any backup files or preserver settings when re-configuring.
Recommend the lasted stable firmware
viewtopic.php?f=14&t=11036
Just because of where it is in the development cycle this this is the most stable build ever.
Re: Restriction exceptions not working
Forgot to ask, are you using a 4 meg router?
if so you need to use 1.6.2
if so you need to use 1.6.2
Re: Restriction exceptions not working
I'm using a WR1043ND V3.
Re: Restriction exceptions not working
I've got same problem on 1.9.2 on a WNDR3800.
When I make restriction for specific ip, or for all except, it has no effect.
Haven't found solution
When I make restriction for specific ip, or for all except, it has no effect.
Haven't found solution
From Nunavik, Quebec, Canada
WNDR 3800 with Gargoyle 1.10.x Dec 18
WNDR 3800 Repeater with Gargoyle 1.10.x
WNDR 3800 with Gargoyle 1.10.x Dec 18
WNDR 3800 Repeater with Gargoyle 1.10.x
Re: Restriction exceptions not working
Agreed, I don't think the restrictions work at all. Set the full restriction works fine but as soon as you add an exception that seems to open it up. The two I have tried are everything restricted with the exception of one web address, made no difference all were allowed and tried with the ip instead same result.
This was from a reflashed 1.9.2 (no config copy) on WNDR3800.
This was from a reflashed 1.9.2 (no config copy) on WNDR3800.
Netgear wndr3700 v2 Gargoyle 1.8.0
TP-Link Archer C7 v2 1.10.X (Built 20180122-0707)
TP-Link Archer C7 v2 1.10.X (Built 20180122-0707)
Re: Restriction exceptions not working
I flashed Gargoyle 1.10.0 onto TPLink WR1043V1 and tested the restriction "All hosts except" still does not seem to work. Force Clients to use DNS Servers ,unchecked. "All Hosts Except" IP , Remote Port Block Only, 53. Hosts with different DNS doesn't get blocked. Seems to be an ongoing problem from previous versions.