Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    Block interfaces from access one another

    Scheduled Pinned Locked Moved Firewalling
    8 Posts 4 Posters 2.6k 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.
    • W
      whiplash
      last edited by

      Yo all,

      I'm trying to figure out how to prevent my management network from accessing the IT network.

      Call management LAN2 and IT LAN1.

      Ultimately I would like to block all traffic to LAN 1 and only allow traffic to specific address and open specific ports. How can I achieve this?

      Thanks
      Whipper

      1 Reply Last reply
      Reply Quote 0
      • E
        Eugene
        last edited by

        Briefly:

        1. a packet is analyzed when it is received on the interface, so you have to create proper rules for incoming traffic.
        2. everything is disabled unless you explicitly enable it.
          So, feel free to create proper rules according your needs and you are done. -)

        http://ru.doc.pfsense.org

        1 Reply Last reply
        Reply Quote 0
        • L
          louis-m
          last edited by

          Hi Eugene. I'm inclined to agree with you on that. i've done 3 installs now and the first 2 did indeed need rules to get things going. the 3rd however decided to let all outgoing through.
          so when i added my vlans, LAN1 could talk to LAN2. these were all various nanobsd installs.
          however, in answer to the original question, just put a block rule in the lan1 interface with source as lan1 and destination lan2.

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

            so when i added my vlans, LAN1 could talk to LAN2. these were all various nanobsd installs.

            Did you make sure that you didnt mix tagged and untagged traffic on the same NIC?

            btw: sorry i mistook the edit-button for the quote-button >_<

            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
            • W
              whiplash
              last edited by

              @louis-m:

              Hi Eugene. I'm inclined to agree with you on that. i've done 3 installs now and the first 2 did indeed need rules to get things going. the 3rd however decided to let all outgoing through.
              so when i added my vlans, LAN1 could talk to LAN2. these were all various nanobsd installs.
              however, in answer to the original question, just put a block rule in the lan1 interface with source as lan1 and destination lan2.

              Thanks for the input, I've tried that but been told that these devices on block outgoing traffic and not incoming. Thats why I am here trying to find out if this is the case or is it possible and how?!

              1 Reply Last reply
              Reply Quote 0
              • W
                whiplash
                last edited by

                nothing conflicting

                1 Reply Last reply
                Reply Quote 0
                • E
                  Eugene
                  last edited by

                  Screenshots of your rules?

                  http://ru.doc.pfsense.org

                  1 Reply Last reply
                  Reply Quote 0
                  • L
                    louis-m
                    last edited by

                    Quote
                    so when i added my vlans, LAN1 could talk to LAN2. these were all various nanobsd installs.
                    Did you make sure that you didnt mix tagged and untagged traffic on the same NIC?

                    probably, 1 of the physical nics is untagged and the 2nd nic has 4 x tagged vlans on it. i haven't tried crossing from 1 vlan to another vlan. i would assume that this wouldn't work. i'll dig a little deeper tonight i think.

                    1 Reply Last reply
                    Reply Quote 0

                    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                    With your input, this post could be even better 💗

                    Register Login
                    • First post
                      Last post
                    Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.
                    Privacy Policy · Cookie Policy