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

    New log type entry?

    Scheduled Pinned Locked Moved General pfSense Questions
    45 Posts 5 Posters 1.0k Views 6 Watching
    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 Online
      stephenw10 Netgate Administrator
      last edited by

      Hmm, you must have something unusual in the ruleset. pfBlocker? Captive Portal perhaps?

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

        @stephenw10 No Captive Portal and no pfBlocker rules on that interface and not updating anyway while I trigger this.

        Unusual is my usual hardware, Hyper-V. But again, this came with 25.07. I will disable Sticky Connections to see if it makes a difference.

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

          The filter log doesn't show a tracker ID so I would start by going through the loaded ruleset for rules without an ID (pfctl -sr) and see if there's a rule that could match. In some special cases rules without logging enabled can still trigger a log.

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

            @marcosm Didn't see nothing. ^^

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

              @marcosm said in New log type entry?:

              In some special cases rules without logging enabled can still trigger a log

              So if I create a block rule with no log and put it on that interface I am good, like with IGMP? Also I could send you the output, it is almost 400 lines though.

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

                You can upload it as a txt file here: https://nc.netgate.com/nextcloud/s/D24QzpR5xeMAdFb

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

                  @stephenw10 Done.
                  Looks like having a block rule on that interface is "fixing" it for my eyes. ๐Ÿ˜‰

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

                    @Bob.Dig Yes, like with IP Options. It could also be useful to get a pcap of the dropped packet.

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

                      @marcosm said in New log type entry?:

                      It could also be useful to get a pcap of the dropped packet.

                      I will look into this tomorrow and upload it. 192.168.216.49 would be the destination IP and I would capture everything with this IP for some seconds.

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

                        A pcap on the external side there would see the traffic before the NAT translation so 192.168.216.49 would not be the destination at that point.

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

                          @stephenw10 On which interface should I capture, I thought on that where the log is from.

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

                            Yes you should pcap on the external interface but you will need to filter by something else because 192.168.216.49 won't be present on those packets at that point.

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

                              @stephenw10 said in New log type entry?:

                              you should pcap on the external interface

                              I filtered only for TCP. Sry for it being that big but I had no success provoking it with just light traffic... Included is the log entry and some pfctl -sr.
                              I hope you guys will find the secret rule. ๐Ÿ˜‰

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

                                Thanks.

                                To be clear though do you have any rules in your ruleset that do not have an ridentifier value set?

                                Within the anchors maybe?

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

                                  @stephenw10 You mean a rule without a description? And what anchors? I can't follow. I am just a GUI-user. ๐Ÿ˜Š

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

                                    I mean in the output of pfctl -sr. In your txt file that is grep'd for ridentifier lines only. A rule that doesn't have an identifier won't set it on the state and could produce logs like this.

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

                                      I didn't mean to leave the grep part in my previous example ๐Ÿ˜…. IIRC that won't show anchor rules so you can run "pfSsh.php playback pfanchordrill" for that.

                                      Bob.DigB GertjanG 2 Replies Last reply Reply Quote 0
                                      • Bob.DigB Offline
                                        Bob.Dig LAYER 8 @marcosm
                                        last edited by Bob.Dig

                                        @marcosm said in New log type entry?:

                                        pfSsh.php playback pfanchordrill

                                        That lists no rules.

                                        ipsec rules/nat contents:
                                        
                                        natearly rules/nat contents:
                                        
                                        natrules rules/nat contents:
                                        
                                        openvpn rules/nat contents:
                                        
                                        tftp-proxy rules/nat contents:
                                        
                                        userrules rules/nat contents:
                                        
                                        1 Reply Last reply Reply Quote 0
                                        • Bob.DigB Offline
                                          Bob.Dig LAYER 8 @Bob.Dig
                                          last edited by

                                          said in New log type entry?:

                                          Looks like having a block rule on that interface is "fixing" it for my eyes. ๐Ÿ˜‰

                                          That turned out not to be the case, still seeing these log entries. ๐Ÿ™

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

                                            Ok and your ruleset doesn't have any lines that don't have an ridentifier?

                                            For example this test box doesn't have any that might block traffic:

                                            [2.8.1-RELEASE][admin@t70.stevew.lan]/root: pfctl -sr | grep -v ridentifier
                                            scrub from any to <vpn_networks> fragment no reassemble
                                            scrub from <vpn_networks> to any fragment no reassemble
                                            scrub on igb0 inet all fragment reassemble
                                            scrub on igb0 inet6 all fragment reassemble
                                            scrub on igb1 inet all fragment reassemble
                                            scrub on igb1 inet6 all fragment reassemble
                                            scrub on igb3 inet all fragment reassemble
                                            scrub on igb3 inet6 all fragment reassemble
                                            scrub on igb0.229 inet all fragment reassemble
                                            scrub on igb0.229 inet6 all fragment reassemble
                                            scrub on ipsec1 inet all fragment reassemble
                                            scrub on ipsec1 inet6 all fragment reassemble
                                            scrub on igb1.50 inet all fragment reassemble
                                            scrub on igb1.50 inet6 all fragment reassemble
                                            anchor "openvpn/*" all
                                            anchor "ipsec/*" all
                                            anchor "userrules/*" all
                                            anchor "tftp-proxy/*" all
                                            anchor "miniupnpd" all
                                            
                                            Bob.DigB 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.