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

    May be a silly question on vLANs and physical interfaces

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    3 Posts 2 Posters 355 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.
    • N
      Nismos4Life87
      last edited by

      Hi everyone,

      First post, so Hi.

      So I have a oddball question, and if it is not feasible, so be it.

      I have a pfS+ box, literally fresh OOB (not out of band) currently only on a 10g SFP fiber to my network, with a management IP associated on the physical port(Lets call it ix1)
      My question is, leaving the ix1 populated with my management IP, and my creating vLans on the port in addition to, will that deleteriously affect my 'physical interface' ip binding on ix1, or will it default that IP as vlan1(my management vlan on the switch)? I am wanting to test something, but the hardware is not colocated in the same location, so I cant just simply do this test by connecting the other interface to another provisioned port. I dont want to lose my connectivity to the pfS box while tossing this idea in.

      N 1 Reply Last reply Reply Quote 0
      • N
        Nismos4Life87 @Nismos4Life87
        last edited by

        It is important to say that I'm trying this in a effort to form a HA based setup, with as minimal as connections, and as easy for the hardware maintenance person to plug and play as possible, in the event of a hardware failure.

        @Nismos4Life87 said in May be a silly question on vLANs and physical interfaces:

        Hi everyone,

        First post, so Hi.

        So I have a oddball question, and if it is not feasible, so be it.

        I have a pfS+ box, literally fresh OOB (not out of band) currently only on a 10g SFP fiber to my network, with a management IP associated on the physical port(Lets call it ix1)
        My question is, leaving the ix1 populated with my management IP, and my creating vLans on the port in addition to, will that deleteriously affect my 'physical interface' ip binding on ix1, or will it default that IP as vlan1(my management vlan on the switch)? I am wanting to test something, but the hardware is not colocated in the same location, so I cant just simply do this test by connecting the other interface to another provisioned port. I dont want to lose my connectivity to the pfS box while tossing this idea in.

        M 1 Reply Last reply Reply Quote 0
        • M
          MushyMiddle @Nismos4Life87
          last edited by

          @Nismos4Life87 I have a very similar setup - my ix1 (10Gb fiber) has all my internal VLANs, and is native VLAN 1 for LAN. This works just fine. The only oddity I've found is mentioned in https://forum.netgate.com/topic/185889/vlan-traffic-showing-up-on-the-wrong-vlan, but is really cosmetic.

          Basically, LAN is ix1. All VLANs are defined with ix1 (lan) as the parent interface. No problems at all. My switch has the default (PVID) of 1 for the port attached to ix1, and all other internal VLANs are passed tagged to the same port.

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