Navigation

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

    Why arn't RFC1918 addresses being blocked?

    Firewalling
    4
    4
    829
    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.
    • H
      Howard2937011 last edited by

      I am stumped with this one…

      I thought that "Block Private Networks" on my WAN interface would block any RFC1918 addresses from leaving my LAN. I recently discovered that this is not true. When I try to access the management interface for my cable modem (192.168.100.1) from a computer on my LAN interface, it shockingly works.

      What's odd, is that if I add a rule on the WAN interface to block all TCP traffic to 192.168.100.1, it doesn't seem to work:

      I tried:

      IPv4 TCP	192.168.100.1	*	*	*	*	none
      

      and

      IPv4 TCP	*	*	192.168.100.1	*	*	none
      

      But neither seem to work. Also as I said, before, I checked "Block Private Networks" so this shows up on my WAN firewall rules:

       	*	RFC 1918 networks	*	*	*	*	*	 	Block private networks
      

      Other than "Block bogon networks" I have no other WAN rules configured. Any advice would be appreciated, thanks.

      1 Reply Last reply Reply Quote 0
      • K
        kpa last edited by

        You're misunderstanding what the option does. It is for blocking inbound connections on the WAN interface, it does not block anything coming from the LAN interface and the network attached to it.

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

          Firewall rules are always (except for floating that can be set) as INBOUND to the interface..

          1 Reply Last reply Reply Quote 0
          • D
            dparring last edited by

            See discussion here:

            https://forum.pfsense.org/index.php?topic=103117.0

            And Wiki HOWTO here:

            https://doc.pfsense.org/index.php/Prevent_RFC1918_traffic_from_leaving_pfSense_via_the_WAN_interface

            DP

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

            Products

            • Platform Overview
            • TNSR
            • pfSense Plus
            • 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