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

    Always getting big red X on connections that are in passlist

    Firewalling
    3
    6
    1.3k
    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.
    • B
      battles
      last edited by

      I am not sure what is going on with this.  As you can see in the 2nd pic, there is what seems to be a block of the two addresses.  In the 1st pic, you can see that both those addresses are in a passlist.  Why is the red X along side the ips that are in the passlist?  (Snort also is pointing to the passlist.)

      pic2.png
      pic2.png_thumb
      pic1.png
      pic1.png_thumb

      pfSense 2.3.4-RELEASE-p1 (i386)
      FreeBSD 10.3-RELEASE-p19
      pfBlockerNG 2.1.2_1
      Snort Security 3.2.9.5_3
      Intel(R) Atom(TM) CPU N270 @ 1.60GHz

      1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator
        last edited by

        So was that a SYN that was blocked or out of state?  Your not showing your full log, nor are you showing your wan rules?  You have a port forward to 49339?  And 9689??

        9689 EMC2 (Legato) Networker or Sun Solcitice Backup (Official)

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.7.2, 24.11

        1 Reply Last reply Reply Quote 0
        • B
          battles
          last edited by

          Not real knowledgeable about what is needed here.

          pic4.png
          pic4.png_thumb
          pic3.png
          pic3.png_thumb

          pfSense 2.3.4-RELEASE-p1 (i386)
          FreeBSD 10.3-RELEASE-p19
          pfBlockerNG 2.1.2_1
          Snort Security 3.2.9.5_3
          Intel(R) Atom(TM) CPU N270 @ 1.60GHz

          1 Reply Last reply Reply Quote 0
          • KOMK
            KOM
            last edited by

            https://doc.pfsense.org/index.php/Why_do_my_logs_show_%22blocked%22_for_traffic_from_a_legitimate_connection

            1 Reply Last reply Reply Quote 0
            • B
              battles
              last edited by

              Thanks KOM.  That has to be the answer and it is nicely explained.  As it said, my connections were going through, so I couldn't understand the X block indicator.  The connections are going to 2 of my own servers and they both do send FIN packets.

              pfSense 2.3.4-RELEASE-p1 (i386)
              FreeBSD 10.3-RELEASE-p19
              pfBlockerNG 2.1.2_1
              Snort Security 3.2.9.5_3
              Intel(R) Atom(TM) CPU N270 @ 1.60GHz

              1 Reply Last reply Reply Quote 0
              • johnpozJ
                johnpoz LAYER 8 Global Moderator
                last edited by

                If pfsense closes the session seeing a fin from your server to the remote client, then sure the response fin,ack could be blocked and logged.

                One way to get rid of such noise would be to just log syn packets.  I turn off default logging and enable a block rule that only blocks syn packets for my log.  So I log attempts to ports that are not open for example say something hits 3389, then sure that is logged.  But other sort of noise like FA packets are not logged.

                An intelligent man is sometimes forced to be drunk to spend time with his fools
                If you get confused: Listen to the Music Play
                Please don't Chat/PM me for help, unless mod related
                SG-4860 24.11 | Lab VMs 2.7.2, 24.11

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