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

    "Default deny rule IPv4 (1000000103)"

    Scheduled Pinned Locked Moved Firewalling
    4 Posts 2 Posters 587 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.
    • W
      wc2l
      last edited by

      I'm seeing some blocked packets. I see it on a few different ports.
      7e3de98a-620a-46e5-8619-a4b9e9a5ee99-image.png

      When I click on the info, I get this:

      a43c3c5a-a50e-4034-b41e-89664e224196-image.png

      To my knowledge, I didn't have these till after I upgraded to 22.05. I know there was an edit to the /usr/local/pkg/pfblockerng/pfblockerng.inc file to fix the high utilization. Does one cause an issue with the other??

      R 1 Reply Last reply Reply Quote 0
      • R
        rcoleman-netgate Netgate @wc2l
        last edited by

        @wc2l said in "Default deny rule IPv4 (1000000103)":

        I didn't have these till after I upgraded to 22.05.

        These what? The default deny rule entries? If I recall correctly they've been there since at least version 1.2
        The 1000000103 rule is a default rule that blocks all things that aren't being allowed by another rule.

        Ryan
        Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
        Requesting firmware for your Netgate device? https://go.netgate.com
        Switching: Mikrotik, Netgear, Extreme
        Wireless: Aruba, Ubiquiti

        1 Reply Last reply Reply Quote 0
        • W
          wc2l
          last edited by

          @rcoleman-netgate Correct.. So when I see this:
          6fb51041-3c6a-4bf3-8786-3206568b5593-image.png

          I click on the red X and I get message:
          753d7e8f-fbf7-4215-9414-246fda31fc45-image.png
          I have the following rule which says to pass the traffic to :
          d00a2a6c-487e-41d8-b340-956ab8763505-image.png

          It is setup the same as many of my other rules that have been configured and working. I'm only seeing it on this port so far. I'm seeing a lot of other ports hitting the network (seems higher, but can't confirm it).

          1 Reply Last reply Reply Quote 0
          • W
            wc2l
            last edited by

            @rcoleman-netgate I think I figured it out.. I was missing the NAT/Port Forward rule!

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