Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Bug: Problem with schedules that go over to the next day

    Scheduled Pinned Locked Moved Firewalling
    18 Posts 6 Posters 2.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • _
      _ToXIc_
      last edited by _ToXIc_

      Hi all, i have a schedule setup for my kids xbox. It all works but there is a problem when the schedule runs into the next day there is a 1min period where you cannot have an allow schedule.

      for example from 8pm to 1am i want them to have internet access but because of the Bug "Error:Start Hour cannot be grater than Stop Hour" i cant create a scheduled from
      20:00 - 1:00
      20:00 - 0:00

      it forces me to schedule 20:00-23:59 then have to schedule 0:00 - 1:00 but there leaves a 1min period where it will drop traffic.

      I'm open to suggestions. thanks for your time.

      0_1527828396859_c76618eb-845c-46a7-91cc-ecff0b34a80a-image.png

      1 Reply Last reply Reply Quote 0
      • MORGiONM
        MORGiON
        last edited by MORGiON

        Block from 1am til 8pm instead.

        Here is how I do my schedule, with a blocking firewall rule on LAN. So they only have access 8am till 9:30pm school nights, 8am till 10:30pm weekends.

        0_1527843209469_0E3FF8F0-43E2-42B7-927B-9D0DABC860C7.png

        P 1 Reply Last reply Reply Quote 0
        • P
          ppmax @MORGiON
          last edited by

          @morgion

          Can you post a screenshot of your LAN rules for this schedule? I'm trying to restrict my kids access in a similar way but I think my rules are the problem.

          Thanks much
          pp

          MORGiONM 1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            Rules cannot span midnight. It is not a bug.

            Make a rule that stops at 23:59 and another from 00:00 to 01:00

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            _ 1 Reply Last reply Reply Quote 0
            • MORGiONM
              MORGiON @ppmax
              last edited by

              @ppmax 0_1528886073392_Untitled.png
              0_1528886149442_Untitled2.png

              P 1 Reply Last reply Reply Quote 0
              • _
                _ToXIc_ @Derelict
                last edited by

                @derelict said in Bug: Problem with schedules that go over to the next day:

                Rules cannot span midnight. It is not a bug.

                Make a rule that stops at 23:59 and another from 00:00 to 01:00

                can this not be change? its blocking internet access for the 1 minute gap/span

                1 Reply Last reply Reply Quote 0
                • KOMK
                  KOM
                  last edited by KOM

                  I've complained about this years ago and nothing has changed. The scheduler is clumsy and clunky. The redo of WebGUI didn't help it at all. I have no idea why it's so primitive. With other firewalls that I use, I can easily create a rule with a schedule that spans midnight or different days and apply it within the rule creation screen. No need to hop around creating multiple schedules and then multiple rules that link to the different schedules.

                  1 Reply Last reply Reply Quote 1
                  • P
                    ppmax @MORGiON
                    last edited by

                    @morgion: thanks for the screenshots. I am using a block rather than a reject...perhaps that's my issue.

                    Here's a screenshot of my LAN rules. the SeboGroup is a collection of of IPs that I want to limit to a specific time range (6AM-11:59PM). As you can see I have another rule for "not" SeboGroup (all other devices) that is not limited to a schedule. Should I disable the default allow LAN rule?
                    0_1528930824562_f02095a4-d216-48f7-973e-13db8d789928-image.png

                    MORGiONM 1 Reply Last reply Reply Quote 0
                    • _
                      _ToXIc_
                      last edited by

                      mine is setup as a block on the lan.. then above it i have an allow with the schedule chosen.

                      P 1 Reply Last reply Reply Quote 0
                      • P
                        ppmax @_ToXIc_
                        last edited by

                        @_toxic_

                        Thanks much for your quick reply ;)

                        So like this? (Note that the rule below the "Allow Kids During Schedule" rule is disabled):
                        0_1528933235232_c5378fbf-9d15-49e2-856a-9c666122e23c-image.png

                        1 Reply Last reply Reply Quote 0
                        • _
                          _ToXIc_
                          last edited by

                          looks good

                          P 1 Reply Last reply Reply Quote 0
                          • P
                            ppmax @_ToXIc_
                            last edited by

                            @_toxic_

                            Thanks. BTW do you use Cron to fire off pfctl -k using these rules?

                            I've been trying for a few days to use allow rules only:
                            allow kidsgroup during scheduled time
                            allow !kidsgroup always

                            After setting these rules I killed all states for IP's in the kidsgroup...but no dice. I thought the preferred methodology with pfsense 2.3.x was using allow vs. block rules since block rules don't kill states?

                            Thanks again
                            PP

                            1 Reply Last reply Reply Quote 0
                            • DerelictD
                              Derelict LAYER 8 Netgate
                              last edited by

                              Try this:

                              Pass kidsgroup schedule
                              Reject kidsgroup
                              Pass any

                              Don't block traffic with pass ! rules.

                              Chattanooga, Tennessee, USA
                              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                              Do Not Chat For Help! NO_WAN_EGRESS(TM)

                              1 Reply Last reply Reply Quote 0
                              • _
                                _ToXIc_
                                last edited by

                                lets not derail the 1min of neither that cannot be in a pass/block schedule

                                1 Reply Last reply Reply Quote 0
                                • MORGiONM
                                  MORGiON @ppmax
                                  last edited by

                                  @ppmax Sorry I didn't get back to you, I've been very busy that last few days.

                                  I thought the preferred methodology with pfsense 2.3.x was using allow vs. block rules since block rules don't kill states?**

                                  Didn't know this one, going to change to this to see if it helps with the Kill States.

                                  1 Reply Last reply Reply Quote 0
                                  • DerelictD
                                    Derelict LAYER 8 Netgate
                                    last edited by

                                    There are no states to kill on a scheduled block rule because no states are created by block rules.

                                    When a block rule schedule fires there is no way to know what states to kill.

                                    When you have a scheduled pass rule that expires, all of the states that have been created by that rule are tagged so there is something to key on to kill the states created by that rule when the schedule expires.

                                    Chattanooga, Tennessee, USA
                                    A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                                    DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                                    Do Not Chat For Help! NO_WAN_EGRESS(TM)

                                    1 Reply Last reply Reply Quote 0
                                    • MORGiONM
                                      MORGiON
                                      last edited by

                                      That makes sense, thank you

                                      1 Reply Last reply Reply Quote 0
                                      • E
                                        edski
                                        last edited by

                                        I've been searching around for the answer to the one minute outage for rule application between 23:59 and 00:00. In my pfSense 2.4.4 setup, I've disabled the default allow all rule and I'm using allow rules for access (based on other guidance I've seen related to states referred to in this post as well). I have two groups of IPs, restricted and unrestricted. I have the restricted group set for 05:00-23:59, 00:00-01:00. The unrestricted group is set for 00:00-23:59. Everything loses access for the one minute between 23:59 and 00:00. Is the only answer to go back to block rules with some sort of cron to kill states (although I've not seen a definitive answer that this will work either)? That seems a bit overly complicated to achieve something so simple. Sorry if this has been solved somewhere. I just haven't been able to find it.

                                        1 Reply Last reply Reply Quote 0
                                        • First post
                                          Last post
                                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.