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

    [solved] pfblockerNG: what does the "permit both"-country-roule allow?

    Scheduled Pinned Locked Moved pfBlockerNG
    6 Posts 2 Posters 2.1k 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.
    • P
      peter808
      last edited by

      As I have seen after generating an automatic roule-set,  pfblockerNG puts an "allow"-rule in the WAN-interface on top of the list if you add a country in pfblockerNG with the list action "permit both". An online security check I have made afterwards states ports 22, 80 and 443 are no open!

      Does that mean that incoming traffic from this permitted country can "make all", i.e. the firewall is completely disabled for IPs of that country?

      1 Reply Last reply Reply Quote 0
      • P
        peter808
        last edited by

        Anyone?

        1 Reply Last reply Reply Quote 0
        • BBcan177B
          BBcan177 Moderator
          last edited by

          You will need to create NAT rules to open up those ports also. Once that is done, any of the IPs in your Permit Alias will be allowed to access those open ports unsolicited.

          "Experience is something you don't get until just after you need it."

          Website: http://pfBlockerNG.com
          Twitter: @BBcan177  #pfBlockerNG
          Reddit: https://www.reddit.com/r/pfBlockerNG/new/

          1 Reply Last reply Reply Quote 0
          • P
            peter808
            last edited by

            In NAT, Pfsense by default activated the option "Automatic outbound NAT rule generation", with LAN to any and any port to any port. I did not change this option.

            So this does mean that ports 22, 80 and 443 were completely open with the pfblockerNG-permit-rule I described above, right?

            1 Reply Last reply Reply Quote 0
            • BBcan177B
              BBcan177 Moderator
              last edited by

              @peter808:

              In NAT, Pfsense by default activated the option "Automatic outbound NAT rule generation", with LAN to any and any port to any port. I did not change this option.

              So this does mean that ports 22, 80 and 443 were completely open with the pfblockerNG-permit-rule I described above, right?

              When creating the NAT Rule, don't auto-create the Firewall rule. Leave that part to the pfBlockerNG package to create. If you let it auto-create, those ports will be wide open to the internet as they are "any" "any".

              "Experience is something you don't get until just after you need it."

              Website: http://pfBlockerNG.com
              Twitter: @BBcan177  #pfBlockerNG
              Reddit: https://www.reddit.com/r/pfBlockerNG/new/

              1 Reply Last reply Reply Quote 0
              • P
                peter808
                last edited by

                ok. thanks for the confirmation, although I think that default behaviour (e.g. auto-creating of "wide-open"-NAT-roules) should be changed.

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