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

    Moving VLANS to ix1 interface

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    17 Posts 4 Posters 1.7k 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.
    • R
      rcoleman-netgate Netgate @cloudjockey
      last edited by

      @cloudjockey said in Moving VLANS to ix1 interface:

      but I cannot get to the internet nor access any of the address on the default LAN vlan (vlan=1).

      You should not really use the default VLAN (1) for anything... I would change your default to 4091 and you'll see things start to move in this case.

      Changing the VLAN # on the 7100 would require changing the built-in port assignments, too, and that can be easily butchered and render the GUI unusable. I always recommend making a single-port interface on the built-in switch on the device before changing the defaults.

      Ryan
      Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
      Requesting firmware for your Netgate device? https://go.netgate.com
      Switching: Mikrotik, Netgear, Extreme
      Wireless: Aruba, Ubiquiti

      C 2 Replies Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate @cloudjockey
        last edited by

        @cloudjockey The untagged VLAN on ix1 is ix1 with no VLAN. Just assign that interface to ix1.

        I agree that one should just pick another VLAN tag and tag it across and avoid mixing tagged and untagged traffic on one interface.

        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
        • C
          cloudjockey @rcoleman-netgate
          last edited by

          @rcoleman-netgate So do I have it right that after moving LAN from LAGG0 with VLAN=4091 to a ix1 interface, all the traffic out of the LAN interface on ix1 is getting tagged as 4091?

          R 1 Reply Last reply Reply Quote 0
          • C
            cloudjockey @rcoleman-netgate
            last edited by

            @rcoleman-netgate What's the best way to create a single port interface on the switch?
            I tried to do this and failed. Here's what I did:

            • Create a new VLAN (55) entry on the switch and assign to EHT8 as untagged with ports 9&10 as tagged
            • Create a new VLAN entry in the interfaces->VLANs table with tag = 55
            • Create a new interface on LAGG0, enabled it and assigned it an IP address (192.168.55.1)
            • Enabled DHCP for the new interface and set up a small pool (192.168.55.2-192.168.55.20)
            • Created a pass-all firewall rule
            R 1 Reply Last reply Reply Quote 0
            • R
              rcoleman-netgate Netgate @cloudjockey
              last edited by

              @cloudjockey said in Moving VLANS to ix1 interface:

              So do I have it right that after moving LAN from LAGG0 with VLAN=4091 to a ix1 interface, all the traffic out of the LAN interface on ix1 is getting tagged as 4091?

              Yes. But on the switch it is PVID on the port and thus goes out untagged (see the Switch Config VLANs tab)

              Ryan
              Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
              Requesting firmware for your Netgate device? https://go.netgate.com
              Switching: Mikrotik, Netgear, Extreme
              Wireless: Aruba, Ubiquiti

              C 1 Reply Last reply Reply Quote 0
              • R
                rcoleman-netgate Netgate @cloudjockey
                last edited by

                @cloudjockey said in Moving VLANS to ix1 interface:

                What's the best way to create a single port interface on the switch?

                My steps:

                1. Create VLAN in pfSense Interfaces->Assignments .... VLANs on LAGG0
                2. create interface with VLAN in the Assignments page
                3. Add VLAN to Switch config (Interfaces->Switches, VLANs tab). UNTAGGED on the port you want it to be isolated to and TAGGED on 9 and 10. Save
                4. Remove the port from all other VLANs it is on (tagged or untagged) by editing each VLAN.
                5. Click on the PORTS tab and change the PVID of that port to the new VLAN # (click the 4091 text under PVID - it will allow editing) then SAVE.
                6. Activate your interface, configure you firewall rules, add DHCP if you want that, etc. This port is now isolated to the single interface.

                Ryan
                Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
                Requesting firmware for your Netgate device? https://go.netgate.com
                Switching: Mikrotik, Netgear, Extreme
                Wireless: Aruba, Ubiquiti

                C 1 Reply Last reply Reply Quote 1
                • C
                  cloudjockey @rcoleman-netgate
                  last edited by

                  @rcoleman-netgate Thanks. That worked. The step I was missing was setting the PVID by clicking the number on the port table in the switch configuration. That interface is not very intuitive.

                  R 1 Reply Last reply Reply Quote 0
                  • R
                    rcoleman-netgate Netgate @cloudjockey
                    last edited by

                    @cloudjockey It does say on the notes at the bottom of the page how to do that.
                    3325f6cf-adbc-46b1-bf16-9a96cc4503b6-image.png

                    Ryan
                    Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
                    Requesting firmware for your Netgate device? https://go.netgate.com
                    Switching: Mikrotik, Netgear, Extreme
                    Wireless: Aruba, Ubiquiti

                    1 Reply Last reply Reply Quote 0
                    • C
                      cloudjockey @rcoleman-netgate
                      last edited by

                      @rcoleman-netgate said in Moving VLANS to ix1 interface:

                      Yes. But on the switch it is PVID on the port and thus goes out untagged (see the Switch Config VLANs tab)

                      Is that always the rule? Would it be correct to say, if a packet going out of a switch port (away from the switch core) has the same VLAN as the port's PVID, the tag gets removed and it becomes untagged.

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

                        @cloudjockey said in Moving VLANS to ix1 interface:

                        @rcoleman-netgate said in Moving VLANS to ix1 interface:

                        Yes. But on the switch it is PVID on the port and thus goes out untagged (see the Switch Config VLANs tab)

                        Is that always the rule? Would it be correct to say, if a packet going out of a switch port (away from the switch core) has the same VLAN as the port's PVID, the tag gets removed and it becomes untagged.

                        Yes, that is the general behavior of switches.

                        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 1
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.