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

    VLAN and Access Point IP assignment

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    2 Posts 2 Posters 319 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.
    • A
      Aved590
      last edited by

      Setting up vLAN for first time. I have a TPLink AX3000 connected to LAN4 and I setup a separate vLAN on LAN4 on my pfSense+ 2100 with 23.09 running. DHCP is running on LAN4 serving out the 18 ip range. If my primary LAN is 172.18.8.0/24 and my vLAN is 172.18.18.0/24, should I set the AX3000 with a static address in the 18 IP range or in the 8 range? Or should I not set a static IP on this? I can configure the AX3000 for a static IP on 8, or 18. I can also tell it to have a dynamic IP. I prefer to know the IP of each of my routers, switches and Access points.

      Recommendations? What's best practice?

      TIA

      1 Reply Last reply Reply Quote 0
      • S
        sic0048
        last edited by

        I would definitely use a static IP address (or at least reserve a static IP address in the DCHP service if you still want to set you equipment up for DHCP connections) for any network hardware (switches, APs, etc).

        Does the AP support VLAN tagging? (Usually it does if the AP supports transmitting several different networks/SSIDs).

        If it does, I don't think it really matters what subnet the device falls on because it will use VLAN tagging in conjunction with your VLAN aware switch to break up the different segments. In that case I would probably have it assigned to the same subnet as all of my other network gear (switches etc) to keep the management of those devices all on the same network subnet.

        If the AP doesn't support VLAN tagging, then you want to make sure the hardware as an IP address in the VLAN you expect it's traffic to use.

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