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

    Can't get an IP on the tagged VLAN/trunk

    Scheduled Pinned Locked Moved DHCP and DNS
    4 Posts 3 Posters 575 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.
    • S
      scottlindner
      last edited by

      I have two first things:

      • I am new to tagged VLANs
      • I don't know if this is the right topic area to post this issue

      I have a Netgate SG-2220 which has one LAN port. I recently purchased a VLAN tagging capable switch so I can provide some separation in my home LAN for security purposes. This seems to be working fine with one exception. I want to have a VM on the Trunk for management purposes so I can restrict access from all VLANs to manage my pfSense firewall and tagged switch. The VM that I have on the tagged VLAN isn't getting an IP address. I am suspecting that may be my issue. What is the VLAN ID for the default LAN in pfSense? I am suspecting there is no VLAD ID at all, but what should the PVID for the port this management VM is on? Or am I really having some crazy DHCP issue?

      1 Reply Last reply Reply Quote 0
      • H
        heper
        last edited by

        @scottlindner said in Can't get an IP on the tagged VLAN/trunk:

        What is the VLAN ID for the default LAN in pfSense? I am suspecting there is no VLAD ID at all, but what should the PVID for the port this management VM is on? Or am I really having some crazy DHCP issue?

        the default lan doesn't have a vlan ID, unless you moved it from the interface to a vlan_interface.

        on the switch end, you'd set this to whatever untagged vlan you want.

        1 Reply Last reply Reply Quote 1
        • S
          scottlindner
          last edited by

          That surprisingly helped immensely. I think the "issue" was that I was tagging it on the port pfSense was on and pfSense was like "I don't know what to do with this tag". Once I untagged it, presto.

          Thanks!

          1 Reply Last reply Reply Quote 0
          • NogBadTheBadN
            NogBadTheBad
            last edited by

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