Page 1 of 1

problem with nat rule to the upgrade to version 6

Posted: Sun Dec 23, 2012 4:27 pm
by leosmendes
I have a couple of rules designed to block access to some customers (address list) that will run from 11:00 PM until 06:00 AM the next day.

for it created a rule that blocks access from 23:00 until 23:59:59
add action=dst-nat chain=dstnat comment=NIGHT dst-address=!172.31.255.2 protocol=tcp src-address-list=night time=23h-23h59m59s,sun,mon,tue,wed,thu,fri,sat to-addresses=172.31.255.2 to-ports=81
and add a second blocking of 00:00:00 to the 06:00:00
add action=dst-nat chain=dstnat comment=NIGHT dst-address=!172.31.255.2 protocol=tcp src-address-list=night time=0s-6h,sun,mon,tue,wed,thu,fri,sat to-addresses=172.31.255.2 to-ports=81
well is not exactly a lock but a redirect to a page with notice of blocking

happens that the second rule is always red, this does not happen in version 5.23. there was some change in the way of spending time for operation of a rule in version 6x?

Re: problem with nat rule to the upgrade to version 6

Posted: Sun Feb 02, 2014 4:19 pm
by leosmendes
update

Re: problem with nat rule to the upgrade to version 6

Posted: Sun Feb 02, 2014 11:19 pm
by ditonet
happens that the second rule is always red
Even between 00:00:00 - 06:00:00 ?
Or you never checked this during mentioned above period of time?
Time rules become red/invalid when they are out of specified time.

HTH,

Re: problem with nat rule to the upgrade to version 6

Posted: Mon Feb 03, 2014 5:08 am
by leosmendes
thanks for the help. this actually happens. to whether the rules were created certar or tested on a schedule of trabaho with rule pointing to the same schedule after certificate that worked just modified the schedule. ps but in version 5x did not happen to turn red. thank you now will migrate to version 6x.