Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    Block private networks - Block bogon networks

    Scheduled Pinned Locked Moved Firewalling
    5 Posts 4 Posters 20.9k Views 1 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.
    • N
      newUser2pfSense
      last edited by

      My WAN interface has the Block private networks… and Block bogon networks checked.
      My LAN interface, 192.168.1/24, and my WLAN interface, 192.168.2/24, do not have either checked.  Do I need to check these for my LAN and WLAN?  I couldn't find the correct answer in the forums.
      Thanks in advance.

      1 Reply Last reply
      Reply Quote 0
      • awebsterA
        awebster
        last edited by

        This is the default configuration.  Do not check block private networks on for LAN or WLAN or you will no longer have access.
        Block private networks: blocks 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 subnets.
        Block bogon networks: blocks any unallocated IP subnets (pfSense pulls a fresh list Monthly).
        These options are designed to prevent someone from using private or bogon IP addresses on the WAN side.

        –A.

        1 Reply Last reply
        Reply Quote 0
        • S
          Soyokaze
          last edited by

          @newUser2pfSense:

          My WAN interface has the Block private networks… and Block bogon networks checked.
          My LAN interface, 192.168.1/24, and my WLAN interface, 192.168.2/24, do not have either checked.  Do I need to check these for my LAN and WLAN?  I couldn't find the correct answer in the forums.
          Thanks in advance.

          You should not check it on your local networks (LAN and WLAN).
          If you don't need external access from WAN side (probably not, because this is not public accessible address), then check it on WAN interface. This will create rule on WAN interface blocking all incoming traffic to WAN interface (but will not interfere with your outgoing packets from LAN/WLAN).

          Need full pfSense in a cloud? PM for details!

          1 Reply Last reply
          Reply Quote 0
          • N
            newUser2pfSense
            last edited by

            Thanks to everyone that replied.  I appreciate it.  I now have my answer.

            1 Reply Last reply
            Reply Quote 0
            • M
              mod
              last edited by

              hi;
              in past versions this was the standard though to block these on the lan as well from 2.3 up i do think and seem to remember. is this a 2.4 base only change/from now on???

              1 Reply Last reply
              Reply Quote 0

              Hello! It looks like you're interested in this conversation, but you don't have an account yet.

              Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

              With your input, this post could be even better 💗

              Register Login
              • First post
                Last post
              Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.
              Privacy Policy · Cookie Policy