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

    Snort time off after 2.2.3 update

    Scheduled Pinned Locked Moved IDS/IPS
    5 Posts 3 Posters 1.1k 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.
    • C
      cjbujold
      last edited by

      Updated to pfsense 2.2.3 and noticed after the update the alert times reported by Snort are showing not the local time but the GMT time for the alerts.

      How can I fix this?

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        That sort of issue is typically a time zone problem. Which specific time zone do you have selected?

        If you are not already using one, try a geographically named zone (e.g. America/New York)

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • P
          pfcode
          last edited by

          @jimp:

          That sort of issue is typically a time zone problem. Which specific time zone do you have selected?

          If you are not already using one, try a geographically named zone (e.g. America/New York)

          for some reason, after upgrade to 2.2.3 from 2.2.2, time zone defaults to the first item of the drop downs,  so I got the same issue,  It seemed that it couldn't find the setting that was set in 2.2.2 (was Canada/Eastern time zone)

          Release: pfSense 2.4.3(amd64)
          M/B: Supermicro A1SRi-2558F
          HDD: Intel X25-M 160G
          RAM: 2x8Gb Kingston ECC ValueRAM
          AP: Netgear R7000 (XWRT), Unifi AC Pro

          1 Reply Last reply Reply Quote 0
          • C
            cjbujold
            last edited by

            Thanks
            Fixed For some reason the upgrade changed the time zone.  The strange part was that PFsense and pfblockerng was showing the correct time on the dashboard but Snort was not.  The timezone I'm using is America/Moncton

            1 Reply Last reply Reply Quote 0
            • jimpJ
              jimp Rebel Alliance Developer Netgate
              last edited by

              What probably happened is that when we updated the time zone data, your old named zone was moved/renamed/deleted and it defaulted since it didn't know what else to do.

              We don't make those edits ourselves, however. We get that data from FreeBSD so it must have changed upstream somewhere.

              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

              Need help fast? Netgate Global Support!

              Do not Chat/PM for help!

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