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

    Only internet traffic rule suggestion

    Scheduled Pinned Locked Moved Firewalling
    6 Posts 3 Posters 578 Views 3 Watching
    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.
    • M Offline
      mrjoli021
      last edited by

      I have several networks. Two of which are a guest network and an IOT network. These networks should ONLY have access to the internet and nothing else. Instead of creating one block rule per network on the Guest and ITO section. Is there an easier way to do this? It is working, but I end up with several rules on each section. Maybe there is a way to consolidate this into one rule.

      JKnottJ 1 Reply Last reply Reply Quote 0
      • JKnottJ Offline
        JKnott @mrjoli021
        last edited by

        @mrjoli021

        I think you have to do it for each network. Here's how I did it.

        e1bc8591-b6ab-46ad-8c70-28dc497a3268-image.png

        PfSense running on Qotom mini PC
        i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
        UniFi AC-Lite access point

        I haven't lost my mind. It's around here...somewhere...

        M 1 Reply Last reply Reply Quote 0
        • M Offline
          mrjoli021 @JKnott
          last edited by

          @jknott

          Thanks that works.

          V 1 Reply Last reply Reply Quote 0
          • V Offline
            viragomann @mrjoli021
            last edited by viragomann

            @mrjoli021
            You can do it with only one flaoting rule if you want. If it should be applied before rules on the interface tabs check the "Quick" option.

            To be on the safe side, I use to add an alias which includes all RFC1918 (private) networks and use this as destination in the firewall rule.
            So to only permit internet access to a subnet, in the pass rule I check "invert" at destination and enter the RFC1918 alias. So this rule allows access to any destination, but RFC1918 networks. And it still matches after adding a new network segment.
            However, you may also use it in a block or reject rule. Rejecting access is basically useful to let the client know that he is rejected and there is no sense for further try. For IoT threre is no need, I think.

            Edit:
            Quick option for floating rules

            M JKnottJ 2 Replies Last reply Reply Quote 0
            • M Offline
              mrjoli021 @viragomann
              last edited by

              @viragomann

              That inverse rule worked out better. I consolidate all the rules into 1 rule.

              thanks

              1 Reply Last reply Reply Quote 0
              • JKnottJ Offline
                JKnott @viragomann
                last edited by

                @viragomann

                In my rules I also allowed for my IPv6 prefix. I have a /56 prefix and one rule blocks it, as well as all ULA addresses, which where included in my Private alias.

                PfSense running on Qotom mini PC
                i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                UniFi AC-Lite access point

                I haven't lost my mind. It's around here...somewhere...

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