RB3011, I’m trying to turn off the internet at night for all devices with dynamic IP. I tried kid control but you have to list every device which is very painful. I’m thinking of just turning off the internet at night for everything that’s in the DHCP server IP range with a firewall rule. Everything that needs to stay on has a static IP (WAP, ATA, TV, etc).
So assuming clients get a dynamic IP in this range:
I’m still looking to just turn off the internet for everyone that’s not in the static list. This includes my laptop, kids devices, my neighbour being on my wifi. Just peace and quiet. The only devices I care about being on are in this list:
Right you are. Caught my copy and paste sloppiness.
Can you help me understand how the list is better than using the src-address approach? It seems to me like the end result is the same, however it forces me to keep a list in parallel.
If you do it by defined interfaces interface list member usage makes sense.
If you have two or more users from different subnets or within a subnet you wish to identify, SOURCE-ADDRESS-LIST (Firewall) makes sense.
If you can identify subnets that are not already interfaces you can use source-address as you have done.
After using object oriented setups on zyxel routers I see the efficiency in the long haul and thus prefer to not work with individual firewall rules if necessary.
For one reason, monkeying with rules is more dangerous, and if I have a good rule, I dont want to touch it.
To change users or access I simply modify the list and rule stays intact.