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

    Possible a bug in design?

    Scheduled Pinned Locked Moved Firewalling
    5 Posts 3 Posters 2.4k 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.
    • A
      alec
      last edited by

      I am new to pfsense, I just installed it and played it around for a while. did some simple test. but I found a major behavior that is different from commercial firewalls. here is my test:

      1. I setup pfsense on a 2 NICs PC with LAN and WAN definition.
      2. The default firewall rule on LAN is to allow any protocols to any(Internet)
      3. I use command ping www.cisco.com -t to test the connectivity to the Internet and it was successfully done and I leave it running in the window.
      4. then I change the rule action from pass to block, the strange thing is that after I click Apply button, the ping still get success??? it is just like the rule does not block it!
      5. Then I stop the ping command by ctl+C, and run it again, and this time, it's timeout and the rule seems to work now?

      I did this kind of testing not only by ping and web page access as well, the result is same!

      My feeling is that the firewall rule change does not affect on the current network session that already exists in the firewall? and it only works when the user initiate a new network request??? I think this is not secure and it is not supposed to be working this way! I also have sonicwall hardware firewall and the rules affects as soon as it has been changed!

      Pls explain.

      1 Reply Last reply Reply Quote 0
      • X
        XIII
        last edited by

        reset the states after making changes and the ping will stop.

        -Chris Stutzman
        Sys0:2.0.1: AMD Sempron 140 @2.7 1024M RAM 100GHD
        Sys1:2.0.1: Intel P4 @2.66 1024M RAM 40GHD
        freedns.afraid.org - Free DNS dynamic DNS subdomain and domain hosting.
        Check out the pfSense Wiki

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

          How often do you change your firewall rules?

          pf considers the rules only when creating a state.
          ipfw checks the rules also for the packets after the state has been created.

          On pfsense pf is used for all "normal" rules and ipfw for the captive portal and scheduled rules.

          We do what we must, because we can.

          Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

          1 Reply Last reply Reply Quote 0
          • A
            alec
            last edited by

            so this is the way pfsense works right? got it…

            1 Reply Last reply Reply Quote 0
            • X
              XIII
              last edited by

              yes, if you stop the ping and restart it, you will see that it now will not work. just reset the states (drops ALL connections) when you want to force a rule change.

              -Chris Stutzman
              Sys0:2.0.1: AMD Sempron 140 @2.7 1024M RAM 100GHD
              Sys1:2.0.1: Intel P4 @2.66 1024M RAM 40GHD
              freedns.afraid.org - Free DNS dynamic DNS subdomain and domain hosting.
              Check out the pfSense Wiki

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