D-Link Forums
The Graveyard - Products No Longer Supported => D-Link NetDefend Firewalls => Topic started by: gmac on September 17, 2014, 12:48:52 PM
-
hello,
I would like to apply time-based rules.
I set up the timer:
(http://autentik.uw.hu/time.jpg)
I have added a rule, but nothing happens, the rule works all day:
(http://autentik.uw.hu/roule.jpg)
I added a routing rule, but nothing happens, the routing works all day:
(http://autentik.uw.hu/route.jpg)
You have any ideas why it does not work?
Thanks
gmac
-
Maybe you have to specify a "Start Date" and "End Date" that tanslates to "forever"?
-
Thanks, but the facory configured timers also do not have a start and end date:
(http://autentik.uw.hu/nonwh.jpg)
Therefore, I believe that this is not the solution.
gmac
-
First, is the date and time on the firewall accurate?
It looks like you have 2 scenarios involving this schedule.
One that is intended to control access to a printer from a particular VLAN, and one to move one VLAN over to WAN2.
For the IP Rule, are you positive that this is the first rule on the list that might match that traffic? If you change the rule to drop, do you lose access to the printer from that VLAN?
For the Routing rule, if you take the schedule off does it correctly direct your traffic as you hope? How are you figuring out which WAN the traffic is routing out of?
-
Dear Rara Avis,
Of course the time settings are fine! I setting up via NTP.
For the IP Rule, are you positive that this is the first rule on the list that might match that traffic? If you change the rule to drop, do you lose access to the printer from that VLAN?
Yes that is my goal. Out from time the VLAN members are not able to print.
For the Routing rule, if you take the schedule off does it correctly direct your traffic as you hope? How are you figuring out which WAN the traffic is routing out of?
My basic goal is the WAN traffic blocking. When the time is up VLAN members can not use the Internet.
Thanks
-
Did you figure out if the IP rule was the only matching rule for the printer traffic?
Did anything change when you changed the rule to drop?
If your goal isn't to change how the traffic is routed, an IP rule would serve you better in the second case as well. Since you obviously already have IP Rule(s) affecting that traffic, I would probably add your new schedule to your existing rule(s).
-
I found the solution. It was very simple: my timer's name was com_time. I deleted the "_" character from the description (the new name is ComTime) and the timer is started.
Outside the timer times not awailable the printer and the WAN.
Thanks for the tips!