Navigation

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

    Blocked Lan to Wan log entries

    Firewalling
    2
    4
    1980
    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.
    • T
      tjadhav last edited by

      Hello guys,
      I have rules that allow any lan net address to reach any WAN address over port 80 and port 443. My last rule is to block any to any.
      Just out of curiosity, my firewall logs indicate traffic being blocked from a lan computer to a wan address using port 80 because of the block any to any rule. Can someone explain why this traffic is being blocked by the last any to any block rule instead of being passed by the lan to any wan over port 80 or 443. I dont have any problems surfing the Internet, just wondering and to get a better understanding of the logs.

      Below are my rules on the Lan interface;
      Proto    Source Port Dest Port
      allow tcp    lannet * *      80
      allow tcp        lannet    *       *     443
      block *     *        * * *

      Below is what I get in my logs;
      Block    LAN     192.168.1.10:56907    207.46.124.107:80 TCP:F
      Block    LAN     192.168.1.10:62461    173.194.35.83:443 TCP:R

      Not sure if TCP:F or TCP:R is whats causing the traffic to ignore the two allow rules and hit the last block rule.

      Thanks in advance

      1 Reply Last reply Reply Quote 0
      • T
        tjadhav last edited by

        no replies :(

        why are some tcp:f and tcp:r using port 80 being blocked from my lan to wan even though I have an allow rule from all lan subnet to wan over port 80?

        Again, no problems connecting to the Internet, just want to understand pfsense.

        1 Reply Last reply Reply Quote 0
        • GruensFroeschli
          GruensFroeschli last edited by

          You don't need to add manually a "block all" rule.
          There is already one invisible below all your rules.

          You most probably see these blocked entries because of this:
          http://doc.pfsense.org/index.php/Logs_show_%22blocked%22_for_traffic_from_a_legitimate_connection,_why%3F

          1 Reply Last reply Reply Quote 0
          • T
            tjadhav last edited by

            Thank you GruensFroeschli; now I understand !

            Are there any other invisible rules?
            If there are any other invisible rules, is there a way to see them?

            Thanks.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post

            Products

            • Platform Overview
            • TNSR
            • pfSense
            • Appliances

            Services

            • Training
            • Professional Services

            Support

            • Subscription Plans
            • Contact Support
            • Product Lifecycle
            • Documentation

            News

            • Media Coverage
            • Press
            • Events

            Resources

            • Blog
            • FAQ
            • Find a Partner
            • Resource Library
            • Security Information

            Company

            • About Us
            • Careers
            • Partners
            • Contact Us
            • Legal
            Our Mission

            We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

            Subscribe to our Newsletter

            Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

            © 2021 Rubicon Communications, LLC | Privacy Policy