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

    Vlans VS multiple interfaces

    Scheduled Pinned Locked Moved Firewalling
    8 Posts 4 Posters 2.0k 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
      while1
      last edited by

      Hello all
      I want to separate several networks.
      Restrict access between LAN TO LAN

      What is better?
      multiple vlans on same physical interface OR multiple physical interfaces on same vlan (0)

      There is another way to limit ports in the LAN?

      Thanks

      1 Reply Last reply Reply Quote 0
      • jahonixJ
        jahonix
        last edited by

        @while1:

        separate several networks … between LAN TO LAN

        You mean Lan1, Lan2, Lan3 etc - e.g. different networks?

        @while1:

        multiple vlans on same physical interface OR multiple physical interfaces on same vlan (0)

        multiple interfaces in the same L2 segment (e.g. a bridge/switch) is highly undesirable in a software based device so a) is your best option.

        @while1:

        There is another way to limit ports in the LAN?

        What? Say again.

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

          Confused as well here.. You ask what is better vlans or physical, and then ask what is better vlans on the same physical interface or putting all the interfaces in the same vlan?  If you did that how you would you isolate them..

          If you have the physical interfaces available and you want multiple networks so you can firewall between them.. Then sure put each interface on its own network.  Now your intervlan traffic that you do allow is not a hairpin.  When vlans share the same physical interface when vlan x talks to y you are hairpinning the traffic in and out the same interface which is a bandwidth hit..  If possible its best to isolate your networks via physical interfaces.. This is why physical interfaces are so valuable on a router..

          If you want devices to be on the same vlan/network use a switch - putting a physical interface on a router (pfsense) in a bridge is normally a BAD use of the port!!

          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.8, 24.11

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

            Thanks.
            I man how to block Lan1 to Lan1 on same subnet
            In fact I ask how to block access within the same subnet and allow traffic only from WAN (i used nat 1:1)

            Aliases AND NAT:
            WAN 60.60.60.60 NAT-1:1 TO LAN 192.168.0.60
            WAN 70.70.70.70 NAT-1:1 TO LAN 192.168.0.70
            WAN 80.80.80.80 NAT-1:1 TO LAN 192.168.0.80
            WAN 90.90.90.90 NAT-1:1 TO LAN 192.168.0.90
            
            Firewall rules
            ALLOW WAN port 80 192.168.0.60
            ALLOW WAN port 80 192.168.0.70
            ALLOW WAN port 80 192.168.0.80
            ALLOW WAN port 22 192.168.0.90
            

            my problem is 192.168.0.90 can access to all subnet without firewall
            the role BLOCK LAN net * * * LAN net - not working for me

            1 Reply Last reply Reply Quote 0
            • jahonixJ
              jahonix
              last edited by

              @while1:

              I man how to block Lan1 to Lan1 on same subnet

              ::)
              You cannot do that.
              That traffic is not going through your pfSense at all, the switch is the only thing involved.

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

                Layer 2 problem

                Cheap d-link switch vvv

                ![Screen Shot 2017-08-02 at 2.37.33 PM.png](/public/imported_attachments/1/Screen Shot 2017-08-02 at 2.37.33 PM.png)
                ![Screen Shot 2017-08-02 at 2.37.33 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2017-08-02 at 2.37.33 PM.png_thumb)

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

                  @jahonix:

                  @while1:

                  I man how to block Lan1 to Lan1 on same subnet

                  ::)
                  You cannot do that.
                  That traffic is not going through your pfSense at all, the switch is the only thing involved.

                  Thank you. Now it's clearer to me.
                  How do you recommend isolating each station?
                  I mean how to do every station will work directly to  NAT 1:1 with as little exposure as possible to LAN
                  (I'm working on vmware environment)

                  1 Reply Last reply Reply Quote 0
                  • jahonixJ
                    jahonix
                    last edited by

                    As Derelict wrote, get a switch which can do private or protected ports or VLANs.

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