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

    Strange Notice after update

    Scheduled Pinned Locked Moved 2.4 Development Snapshots
    6 Posts 4 Posters 1.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.
    • D
      dcol Banned
      last edited by

      Just updated to latest dev version and got this Notice 3 times when pfsense came up

      Unresolvable destination port alias '137-139-137-139' for rule 'm_Other SMB2 outbound'

      I do not have any rule matching this.
      What would cause this?
      Notice.jpg
      Notice.jpg_thumb

      1 Reply Last reply Reply Quote 0
      • P
        phil.davis
        last edited by

        There was a change to better validate for a missing port alias and report the problem:
        File a notice and omit rule(s) using a missing port alias.
        But the change missed out the case of a port range being specified. That was fixed in commit:
        https://github.com/pfsense/pfsense/commit/dd844c430622fa68de1f868b62ec375d7131ce16

        For about 24 hours there would have been some snapshot(s) with the problem you are seeing. It should be fixed in the latest snapshots, so upgrade again and try it.

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

        1 Reply Last reply Reply Quote 0
        • D
          dcol Banned
          last edited by

          Upgraded today and still seeing the same Notices.

          Here is my release
          2.4.0-BETA (amd64)
          built on Sun Mar 26 00:06:28 CDT 2017
          FreeBSD 11.0-RELEASE-p8

          Is there something else I need to do?

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

            Looks like a bug in the traffic shaper wizard.. After running though the traffic_shaper_wizard_dedicated.xml and selecting smb priority on the last screen it makes a invalid rule..

            Check your floating rules that mention 137-139 edit and save that rule again it will 'fix' the rules port range.

            1 Reply Last reply Reply Quote 0
            • D
              dcol Banned
              last edited by

              Yes, I see it is set by the traffic shaper in the floating rules. I resaved it. let you know if I see it again. Thanks

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

                I fixed the shaper code that made the bad rule. If you edited/saved the rule you should be OK. Anyone else that upgrades and hits this can either edit/save or remove the wizard and re-run it, assuming they're on a snap which includes the fix.

                https://redmine.pfsense.org/issues/7434

                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.