Rules + Schedules Ineffective?
-
- Create a rule on your WAN interface like this: Action Block / Protocol Any / Source Any / Destination 'Children' / Schedule 'AccessDenied'
Note: This rule is not needed in any normal installation. The WAN will already have a general block at all times, and in any case there will be no traffic initiated from the real public internet with destination IPs in 'Children', because 'Children' is a bunch of private IP addresses in the LAN behind pfSense.
-
Thanks for your precision Phil.
It will help me to simplify my ruleset a bit.Merry X-Mas :)
-
There is a cron scheduler, I wander if you could setup a state flush just a minute after your block rule goes into effect.
Hello One and All,
That was how I got around the drama. Downside is that when holidays arrive, I forgot to remove the cron scheduler to kill all states. Unhappy son (and me as well at times) until I woke up.
I am relieved that the thread I started was not just me being dull or failing "to see the forest for the trees" and glad it has triggered some discussion.
@derf, I am about to upgrade from 2.0.3 to the latest and once that is complete, I will then go through your steps. I also understand phil.davis remark about the WAN element.
Nonetheless, does anyone know whether or not this part of pfSense will be (or has been) addressed? As for the latter part of that question, I will soon find out. …....upgrading in 5 minutes. Wish me luck!
Hope we all had a fab Christmas and may 2014 be superb!!!
-
Good Luck OzRattler, may all your overs be wicket maidens…. ;-)
-
I would like to see that in the base code of a rule with a schedule.
I have used this and it works great. Thanks.Phil.Davis, this was not to block incoming, but to block outgoing once the block schedule was in place. While it is true it is not needed in normal rule sets, but any rule that has a schedule on it, needs to have the states killed once it is supposed to be blocking. Or at least an option to kill the states. I can think of a situation where the rule should not drop states. This would be in a rule sending traffic to another shaping queue. This might help make sure the correct traffic shaping is used, but would interrupt the current session, which is probably unwanted.
-
I tried it without that ""Allow_internet" rule and then open states remain open…. somehow.
Also I noticed that some states from floating rules remain open (sometimes) with that both allow and stop rules active.
Thinking of moving those allow-stop rules to floating or wan area to see what will happen.Pere, did you make any headway with your workaround for the "Schedule States" bug? I thought I'd re-invented your solution, but it only worked in testing. When I dropped my rules into a live environment they are failing to remove active states. I feel that I will need to hardcode a crontab script to call pcftl.
On a side note… can anyone point me to the documentation for pfSense's version of the pfctl command?
-
I'm on 2.1.5 and the issue still persists. At 8pm I want the connections to be passed over to a 2nd vpn since the first vpn gets very slow at night.
It correctly works if I turn a machine on past 8pm, the connection goes through the 2nd vpn. However for computers already on, they don't move over.
Is there a fix without using cron?
-
-
Schedules do work properly with no hassle on 2.2 release.
Thanks pfsense devs :D -
They still don't work quite right for me in 2.2-RELEASE. I set up a schedule for 5pm to 10pm, then created two rules: one passes TCP packets, the other passes UDP packets. Outside the scheduled time the rules don't exist and the default block rule drops packets. When 10pm rolled around, the TCP rule took effect, the TCP states were reset, and further TCP connections were blocked. But the UDP states continued operating and the game the rule was intended to disable continued running.
I ran pfctl -s rules from the console and the pass rules for both TCP and UDP are gone, so it's apparently just that the existing UDP states were not reset when the schedule expired.
-
Updating that I have today moved across to 2.2 and just fixing other minor issues - such as the Console won't display options etc.
I will be watching how the Schedules go especially since I toughened them up via CRON and flushing ALL states after the start time of any set schedule.
Finger's are crossed!!!!
Oz
-
I'm on 2.2.6 and behavior persists with certain state types. I understand the logic behind the handling of states, but the schedule should work.
Have a son who has learned to use betternet vpn, which keeps a state open, unfortunately. In turn, this allows him full internet access after he's supposed to have it.
EDIT:
The bug supposed to address this (will find number and add to this post) seems not to have addressed the issue at all.In System - advanced - misc: (which BTW is a stupid place to bury this option) the option "schedule states" shows an unchecked checkbox by default. According to the explanation:
"By default, when a schedule expires, connections permitted by that schedule are killed. This option overrides that behavior by not clearing states for existing connections"
The default behaviour of schedules should be as explained, but active states remain persistent after schedule block occurs.
Is this a reopen bug issue? I don't think the bug should be closed.
-
pfsense - 2.2.6
I've removed the default allow rule and setup allow rules permitting access.
Works great for all but UDP.
There appears to be no solution so I'm now going to play with placing the default allow back in and utilising the traffic shaper to kill data flow between certain times.
I have my Fingers crossed.If there's a thread that I've missed with a solution (apart from the cron job) please let me know!
Thank you!
-
Has this been fixed or has someone found a reliable work-around?
-
I'm on 2.2.6 and still experiencing this issue.. : https://forum.pfsense.org/index.php?topic=108943.0
Waiting for a solution.. -
Any updates?
I am having an issue using a scheduled block on Steam ports -states not clearing automatically..
-
Could someone please have a look at my LAN rules?
I have Steam ports as an alias ' Steam' on 2x different schedules..
The goal is to block Steam at a scheduled time however, the states do not flush ?
Am I doing something wrong?
-
Anyone? :o
-
Anyone have an update on the UDP states issue?
-
Bump?