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

    Missing rule and alias

    Scheduled Pinned Locked Moved Firewalling
    2 Posts 2 Posters 154 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.
    • K
      konacat
      last edited by

      I am running CD 2.72 and are newish to pfsense. I added a permit rule (outbound) and alias via ASN a while back that I need to delete. The rule and alias do not appear in their correct areas under pfblockerng (newest one.) The Reports section show that the rule exists. I do not have an old backup of the config. I thought that I would ask if there is another way to remove the permit rule (outbound?)

      Thanks!

      JonathanLeeJ 1 Reply Last reply Reply Quote 0
      • JonathanLeeJ
        JonathanLee @konacat
        last edited by

        @konacat under LAN it should show a outbound rule make sure you make rules for web traffic and all the ports you need and once that is done delete the pre configured rules.

        Reference this:
        https://docs.netgate.com/pfsense/en/latest/firewall/configure.html

        Keep in mind you need your firewall to be accessible to access the GUI for admin needs, if you mess up that rule it is ok you can console in and set it back.

        If that happens
        Reference this:
        https://docs.netgate.com/pfsense/en/latest/troubleshooting/locked-out.html

        If you looking for NAT (network address translations

        Reference this:
        https://docs.netgate.com/pfsense/en/latest/nat/outbound.html

        Also last one for aliases...

        Reference this:
        https://docs.netgate.com/pfsense/en/latest/firewall/aliases.html

        Hope that helps I would work methodically first make a rule for the GUI so you don't get locked out and after make a list of needs and create rules for it.

        Keep in mind WAN will block everything inbound unless it originated from LAN going outbound requests and return traffic. It is really secure by default. Again you can really lock it down like Fort Knox if you want and protect the Heidelberg printing presses. (hypothetically speaking)

        Make sure to upvote

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