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

    blocking traffic between interfaces

    Scheduled Pinned Locked Moved Firewalling
    10 Posts 6 Posters 5.2k 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
      aminbaik
      last edited by

      Hello,
      I am using pfsens with the last version and I have multi interfaces:
      wan: 192.168.0.2/24 with gw 192.168.0.1
      lan 192.168.1.1/24
      wifi 192.168.2.1/24
      management 192.168.3.1/24
      I want to allow lan and wifi using internet but not routing between them.
      I want to allow port 80 from wifi to lan.
      I want to allow management can route to lan and wifi but no internet working on it.
      I want to allow management ip 192.168.3.2 can route to lan and wifi and have internet access.
      I am using manul nating and enable it only from lan to wan and wifi to lan and management to wan
      I try to make that with multi ways but I didn't success.
      so what the rule should I have to do ?
      thanks.

      BabizB 1 Reply Last reply Reply Quote 0
      • KOMK
        KOM
        last edited by

        Nobody is going to write all your rules for you. Show us what you have done and we can make corrections if there are mistakes.

        One mistake a lot of people make is that they forget to clear the existing states after changing the rules. Existing states will NOT be affected by a new rule or modifying an existing rule.

        1 Reply Last reply Reply Quote 1
        • T
          tman222
          last edited by

          I would read a little here first to understand how the pfSense firewall works and how to setup and configure rules:

          https://www.netgate.com/docs/pfsense/book/firewall/index.html

          If you have any questions after that, please let us know and we can help you with specifics.

          Hope this helps.

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

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • A
              aminbaik
              last edited by

              pls check the attached file:
              0_1543160911713_112.png
              thanks.

              1 Reply Last reply Reply Quote 0
              • johnpozJ
                johnpoz LAYER 8 Global Moderator
                last edited by johnpoz

                Dude post a screenshot of your rules tabs

                example
                0_1543161920028_ruletab.png

                An intelligent man is sometimes forced to be drunk to spend time with his fools
                If you get confused: Listen to the Music Play
                Please don't Chat/PM me for help, unless mod related
                SG-4860 24.11 | Lab VMs 2.7.2, 24.11

                1 Reply Last reply Reply Quote 0
                • BabizB
                  Babiz @aminbaik
                  last edited by

                  @aminbaik said in blocking traffic between interfaces:

                  Hello,
                  I am using pfsens with the last version and I have multi interfaces:
                  wan: 192.168.0.2/24 with gw 192.168.0.1
                  lan 192.168.1.1/24
                  wifi 192.168.2.1/24
                  management 192.168.3.1/24
                  I want to allow lan and wifi using internet but not routing between them.
                  I want to allow port 80 from wifi to lan.
                  I want to allow management can route to lan and wifi but no internet working on it.
                  I want to allow management ip 192.168.3.2 can route to lan and wifi and have internet access.
                  I am using manul nating and enable it only from lan to wan and wifi to lan and management to wan
                  I try to make that with multi ways but I didn't success.
                  so what the rule should I have to do ?
                  thanks.

                  If you want to "isolate" subnet , you can do it in few clicks, just assign your gateway under your lan firewall rule "any to any", go trought "advanced tab" and swap Gateway "Default *" to your gateway specific name.

                  alt text

                  And rule looks like this:
                  alt text

                  Additionally you can block incoming tcp/udp packets, from other interfaces by adding specific blocking rule at top of your interface rules grid for extra secure, but usually is enough specific only gateway than default. Check this by yourself!
                  Cheers.

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

                    No.

                    Do not rely on routing to block traffic.

                    If you do not want DMZ hosts to access LAN hosts, then block traffic on DMZ to destination LAN network.

                    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
                    • A
                      aminbaik @Babiz
                      last edited by

                      @babiz
                      thank you so much … its working now :)

                      1 Reply Last reply Reply Quote 0
                      • BabizB
                        Babiz
                        last edited by

                        Yes @aminbaik , but same as @Derelict said, is not best pratiche, (forcing gateway on standard firewall rule to rely "blocking stuffs" at routing stage instead a proper firewall rule), anyway for smallest enviroments just work enough, I have this kind of configuration because here is no bigger hackers 🍹 and I not noticed any issue related this kind of basic rule setting..
                        Goodbye!

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