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

    Snort - Network Interface Mismatch

    Scheduled Pinned Locked Moved pfSense Packages
    18 Posts 4 Posters 9.4k 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.
    • K
      kilthro
      last edited by

      when you removed that bogus line did it remove the entry in the interfaces menu? I removed my re0/ and havent rebooted yet but was wondering if it would update the menu. I was using the menu  to see if the ghost interface was there before I would reboot.

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

        FYI- if you edit the config at the command line, be sure to rm /tmp/config.cache when finished.

        If you use the viconfig shortcut, this is handled automatically.

        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
        • jimpJ
          jimp Rebel Alliance Developer Netgate
          last edited by

          I found a case where it might be possible that the interface could be duplicated in certain conditions under snort.

          If you could reinstall snort any time after 10:20am EDT today and then try to see if you can replicate the issue again.

          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
          • K
            kilthro
            last edited by

            @jimp:

            I found a case where it might be possible that the interface could be duplicated in certain conditions under snort.

            If you could reinstall snort any time after 10:20am EDT today and then try to see if you can replicate the issue again.

            Excellent I will try that then.@jimp:

            FYI- if you edit the config at the command line, be sure to rm /tmp/config.cache when finished.

            If you use the viconfig shortcut, this is handled automatically.

            I just edited the file via the webgui / edit file area. Can I just browse to the tmp location and delete the cache? Dont have a keyboard hooked up t the system at the moment.

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

              Actually I found one more place that is more likely to have caused the problem. Reinstall again if you haven't yet done it.

              As for editing via the GUI, you can rm /tmp/config.cache by Diagnostics > Command, and then just edit/save anywhere in the GUI to trigger a filter sync.

              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
              • K
                kilthro
                last edited by

                @jimp:

                Actually I found one more place that is more likely to have caused the problem. Reinstall again if you haven't yet done it.

                As for editing via the GUI, you can rm /tmp/config.cache by Diagnostics > Command, and then just edit/save anywhere in the GUI to trigger a filter sync.

                Ok thanks. I will be able to do this later this evening. I appreciate the quick turn around on this.

                1 Reply Last reply Reply Quote 0
                • jnorellJ
                  jnorell
                  last edited by

                  I just updated the package, and it still has a problem.  I deleted the "bad" line in config.xml and removed config.cache, went to snort Global Settings and hit save - at this point config.xml is still ok, I then hit Apply and it adds a bad line.

                  It's slightly different now, previously it was "<re0>" and now it's "" … but still there.</re0>

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

                    So at least it seems we're on the right track… :-)

                    I'll look for any other places where it might be doing anything like that kind of thing.

                    I made some changes in the base OS as well to see if things there might be affected, might not be in the next snap, but the one after it should have them.

                    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
                    • jimpJ
                      jimp Rebel Alliance Developer Netgate
                      last edited by

                      OK, Efonne spotted another place that could have done this and I committed a fix and bumped the version of the snort package. Try it again, if you can.

                      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
                      • jnorellJ
                        jnorell
                        last edited by

                        @jimp:

                        OK, Efonne spotted another place that could have done this and I committed a fix and bumped the version of the snort package. Try it again, if you can.

                        I think you've got it fixed.  However:

                        In testing again, I fixed the config file, removed the config.cache, verified the config was fixed (and even changed/saved a firewall rule to verify the save there didn't have the problem) - now updated to snort package version 1.35.  I checked the config at this point and the "" was back again.

                        I fixed the config again, removed config.cache, and hit the snort Global Settings tab.  save, apply … seems to be fixed.  I ran around a number of snort menus and the problem didn't recur.

                        So... just beware you have to fix your config one last time after you update from a "bad" version (1.34).

                        1 Reply Last reply Reply Quote 0
                        • K
                          kilthro
                          last edited by

                          Excellent work everyone! I will keep that in mind once I am able to test it.

                          1 Reply Last reply Reply Quote 0
                          • K
                            kilthro
                            last edited by

                            Your fix on the snort package did the trick. I uninstalled/installed latest version and then attempted same save on the global settings and no more duplicate device. :-)

                            I didnt have the issue as posted above of having to delete the duplicate again (fixing the config file again)… Mine was good to go and I tried a few times with saving settings and no problems.

                            Thanks again for the quick fix to this issue!!!

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