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

    Reloading every 15 minutes: ipfw-classifyd: Reloading config… Why?

    Traffic Shaping
    2
    5
    2.8k
    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.
    • N
      Nachtfalke
      last edited by

      Hi,

      I am using layer7 filter for some protocols.
      I got every 15min this output in system log:

      Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: xunlei (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: thecircle (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: tesla (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: soulseek (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: soribada (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: pplive (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: poco (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: napster (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: mute (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: kugoo (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: ipp (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: gnutella (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: fasttrack (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: edonkey (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: directconnect (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: bittorrent (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: audiogalaxy (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: applejuice (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Loaded Protocol: 100bao (rule action block)
Nov 13 00:15:02 	ipfw-classifyd: Reloading config...
Nov 13 00:15:02 	php: : Sending HUP signal to 19198

      This seems to be "ok" because in cron I found this line:

      0,15,30,45  	*  	*  	*  	*  	root  	/etc/rc.filter_configure_sync 

      My question are:
      1.) Why is it neccessary to reload this filter every 15min ?
      2.) Is it possible to change these settings to a longer time like every 6hrs without (bad) influencing the layer7 filter ?
      3.) Is it possible to silent the system log output for layer7 ?

      Thank you for your feedback!

      1 Reply Last reply Reply Quote 0
      • E
        eri--
        last edited by

        Normally that is added by some port or something.
        but its not strictly required on 2.0.

        1 Reply Last reply Reply Quote 0
        • N
          Nachtfalke
          last edited by

          Hi,

          I found out that this cron entry is from the scheduler. If I create a schedule this entry is added.
          The output of the layer7 filter is only a side effect.

          So my question a little bit modified again:

          1.) Is it a problem for scheduler usage if I increase the cron time from 15min up to 6h ?

          Or does this mean that if I have a schedule which blocks traffic at 7am and the cron job executes at 6am and 12am that the schedule will take effect at 12am first ?

          Thanks for feedback.

          1 Reply Last reply Reply Quote 0
          • N
            Nachtfalke
            last edited by

            I it with this cron job possible to only reload the filter at
            6:30am and 6:00pm ?

            0,30 	6  	*  	*  	*  	root  	/etc/rc.filter_configure_sync 

            It would help me in my special scenario so that my system log will not be spammed every 15min but the scheduler/filter will reload at the time when it is needed ?

            1 Reply Last reply Reply Quote 0
            • N
              Nachtfalke
              last edited by

              hi again.

              I changed the cron entry a little bit so it suits my setup.

              Perhaps for future pfsense relases this could be realized that there aren't so many (unneccessary) filter reloads.
              In a scheduler I have to define a start time and an end time. every time needs an "hour" and a "minute". per haps it can be realized that the minutes and the hours could be entered in the cron job.

              So lets say:
              Start:
              [hour1]: 6
              [minute1]: 0

              End:
              [hour2]: 17
              [minute2]: 30

              out of these times we can create a cron job like that:

              [minute1],[minute2] 	[hour1],[hour2]  	*  	*  	*  	root  	/etc/rc.filter_configure_sync 

              I am no coding expert and I do not know what is behind the scenes but it is an idea :)

              1 Reply Last reply Reply Quote 0
              • First post
                Last post