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

    New Router. Backup Restored. No Snort Alerts now

    Scheduled Pinned Locked Moved pfSense Packages
    snortalertsnot working
    3 Posts 2 Posters 437 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.
    • L
      LeiShen
      last edited by

      Hi,

      I upgraded my router from a J1900 router to an N100. After installing pfSense CE 2.7.2, I restored a current backup and Snort failed to install. So I manually installed Snort and verified that all the Interfaces were correctly configured as before, active and enabled, and that all the updates to the Rule Sets where current (it appears to have saved the configuration from the backup and applied it once Snort was manually installed).

      But Snort has not reported any alerts since the upgrade from 3 weeks ago, whereas before it would report a few alerts every day.

      Suggestions on where to look for clues on what's going wrong?

      Thanks

      1 Reply Last reply Reply Quote 0
      • bmeeksB
        bmeeks
        last edited by

        Did your network interface names change by chance? For instance, if your new hardware contains different NIC hardware than your old hardware, then the physical interface names will have changed and that can confuse Snort (especially if it was restored from a configuration based on the old physical interface names).

        If you hardware NICs changed, I suggest deleting all the Snort interfaces and then creating them again.

        L 1 Reply Last reply Reply Quote 1
        • L
          LeiShen @bmeeks
          last edited by LeiShen

          @bmeeks :
          Ok. So I disabled and unassigned the WAN Sort interface. Then copied it back to the newly unused WAN interface, enabled and started it and...... IT WORKED!!! I'm getting Alerts and its generating blocks as before the upgrade!

          Same name as before, but apparently an internal interface mapping in Snort was still looking for the old WAN interface id.

          Thanks!!!

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