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

    Floating vs WAN rule

    Scheduled Pinned Locked Moved Firewalling
    4 Posts 3 Posters 1.6k 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.
    • D Offline
      duren
      last edited by

      I'm doing a test rule, trying to block pinging www.google.com (ping typically hits 216.58.208.36)

      BLOCK, protocol any, destination: network 216.58.0.0/24

      • When I make a floating rule, targeting only the WAN interface, it correctly blocks.
      • When I make a WAN rule, it doesn't block

      Why is that?

      pfSense 2.3. Can someone verify?

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

        The non-floating rules apply only to traffic coming IN on an interface. In other words the pings you're using for testing your rules are going OUT on the WAN interface and the non-floating rules won't apply to the them.

        1 Reply Last reply Reply Quote 0
        • D Offline
          duren
          last edited by

          RTFM fail  :-[

          On a separate but related out direction note..

          I'm now kind of confused as to why I'd have a host rule defining an alternate gateway (VPN) in the LAN section because typically you would think that the traffic needs to flow in AND out over this alternate gateway and since out is only on floating rules, shouldn't mine be a floating rule?

          1 Reply Last reply Reply Quote 0
          • DerelictD Offline
            Derelict LAYER 8 Netgate
            last edited by

            When you want to route traffic out a certain gateway (VPN or not) you want to match the traffic when the state is being created. That happens on LAN when a LAN host starts a connection. It really is the easiest/best place for the policy routing rule.

            You have to have a rule there passing the traffic anyway. It might as well just do the policy routing too.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

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