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

    24.03.r.20240416.0005 : all ok.

    Scheduled Pinned Locked Moved Plus 24.03 Development Snapshots (Retired)
    20 Posts 7 Posters 1.3k 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.
    • stephenw10S
      stephenw10 Netgate Administrator @Gertjan
      last edited by

      @Gertjan said in 24.03.r.20240416.0005 : all ok.:

      ( the GIMP firewall log spammer is still there )

      You mean IGMP?

      GertjanG 1 Reply Last reply Reply Quote 1
      • GertjanG
        Gertjan @stephenw10
        last edited by

        @stephenw10

        Euh, yes, that one.

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          I've not seen that, what are you seeing?

          GertjanG 1 Reply Last reply Reply Quote 0
          • GertjanG
            Gertjan @stephenw10
            last edited by Gertjan

            @stephenw10

            The upper 4 ones ....

            b6013402-2a3e-46d9-981a-deeb2f952291-image.png

            In the beginning, I had only 3 LAN firewall rules.
            The latter two are the obvious pass all rules. No thrills, bells and whistles.
            I had to create the first "IGMP" rule : a simple pass rule with this option set :

            ab5dc3bc-ebb3-4b46-80fc-c35c004fea43-image.png

            so now I have :

            5ac507f0-036b-4e34-bb9b-82a70fa55bc9-image.png
            and no more IGMP log activity.

            Take note : my non logging main pass rule 1712736749 rules had not the log option checked, it was still logging ...

            See also : [Multiple users] 24.03.r.20240410.1729 IGMP block gets logged

            No "help me" PM's please. Use the forum, the community will thank you.
            Edit : and where are the logs ??

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Ah, interesting. I would expect to need IP Options set there to pass IGMP traffic. But it shouldn't be blocked by an pass rule, it should hit the default block rule. Hmm

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Oh OK I see this has been discussed in a ticket already: https://redmine.pfsense.org/issues/15400

                GertjanG 1 Reply Last reply Reply Quote 0
                • GertjanG
                  Gertjan @stephenw10
                  last edited by

                  @stephenw10 said in 24.03.r.20240416.0005 : all ok.:

                  ticket already: https://redmine.pfsense.org/issues/15400

                  Yeah, just found it : Had to look in the regression list.
                  And the issue is already solved, as this should be seen as a feature.

                  A potential issue still stands : a non logging pass rules starts to log firewall 'drop' lines : that one will get questions ...
                  Also : filling up a log with potential "no so easy to explain" drop log lines can hide quickly other, more useful info.

                  No "help me" PM's please. Use the forum, the community will thank you.
                  Edit : and where are the logs ??

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Yup I agree. It confuses me!

                    1 Reply Last reply Reply Quote 0
                    • M
                      marcosm Netgate
                      last edited by marcosm

                      I think that ultimately it's a non-issue. The logging "quirk", from what I've seen, only applies when the rule specifies IGMP. It's safe to assume that a user seeing the logs must have been trying to do something with IGMP, and this new behavior makes it obvious they did something wrong (allow-opts). It's been suggested that something could be added to the GUI when IGMP is selected, but I'm not convinced we should be adding protocol-specific info. Maybe a good middle ground is to automatically expand advanced options and check the IP options checkbox.

                      Bob.DigB 1 Reply Last reply Reply Quote 1
                      • Bob.DigB
                        Bob.Dig LAYER 8 @marcosm
                        last edited by Bob.Dig

                        @marcosm said in 24.03.r.20240416.0005 : all ok.:

                        The logging "quirk", from what I've seen, only applies when the rule specifies IGMP.

                        No.

                        M 1 Reply Last reply Reply Quote 0
                        • U
                          Uglybrian
                          last edited by

                          Screenshot from 2024-04-17 08-22-05.png

                          Where is this setting found?

                          GertjanG 1 Reply Last reply Reply Quote 0
                          • M
                            marcosm Netgate @Bob.Dig
                            last edited by

                            @Bob-Dig Hah yeah I proved myself wrong right after posting.

                            1 Reply Last reply Reply Quote 2
                            • GertjanG
                              Gertjan @Uglybrian
                              last edited by

                              @Uglybrian said in 24.03.r.20240416.0005 : all ok.:

                              Where is this setting found?

                              79507202-24e9-452f-88f1-8826e7ce930e-image.png

                              and see the pure pf power being unfolded for you 😊

                              No "help me" PM's please. Use the forum, the community will thank you.
                              Edit : and where are the logs ??

                              1 Reply Last reply Reply Quote 3
                              • M
                                mikey_s
                                last edited by

                                It prob took 30 minutes + for the update to 24.03.r.20240416.0005 yesteday and after that it wouldn't pass traffic or allocate DHCP addresses etc.

                                I had to console onto the unit originally to see what the console was saying.

                                Rebooted and then the system started working again. This is on "white box" hardware.

                                1 Reply Last reply Reply Quote 0
                                • stephenw10S
                                  stephenw10 Netgate Administrator
                                  last edited by

                                  Hmm, what did you update from?

                                  Then after the reboot it was running the new RC OK? Anything logged when it wasn't responding?

                                  M 1 Reply Last reply Reply Quote 0
                                  • M
                                    mikey_s @stephenw10
                                    last edited by mikey_s

                                    @stephenw10

                                    Previous 24.03 RC release

                                    When I connected via a console cable it looked like DNS failures.

                                    All appears to be working post 2nd reboot.

                                    Is there a log file you wish me to attach?

                                    P 1 Reply Last reply Reply Quote 0
                                    • stephenw10S
                                      stephenw10 Netgate Administrator
                                      last edited by

                                      The latest upgrade log in /conf might show something. But only if it has errors. Otherwise the system log should have recorded any failures at the first boot.

                                      1 Reply Last reply Reply Quote 0
                                      • P
                                        pfsjap @mikey_s
                                        last edited by pfsjap

                                        @mikey_s Check if you have the same error msg (unbound) in the system log as in the first post of this thread 24.03-BETA to 24.03-RC update hiccup. Unbound did not start => DNS not working.

                                        I too had to reboot once more after the update reboot.

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