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

Clients not getting IP from vlan

Scheduled Pinned Locked Moved L2/Switching/VLANs
4 Posts 2 Posters 214 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
    anishkgt
    last edited by anishkgt Mar 12, 2024, 4:07 PM Mar 12, 2024, 4:06 PM

    Hello,

    Bought the 2100 appliance couple for days ago. Its working well so far.

    I have setup Vlan 30 on lan and assigned it switch port 2. Then enabled it with an IP 172.16.30.1. Assigned it to port 2 where a wireless LinkSys router configured as a bridge is connected.
    Enabled the DHCP server as well. When connecting to this wireless network, the client (my laptop) does not get an IP. I tried enabling 'tagged' as well. Also added firewall rule to allow the new vlan to communicate from and to any using any port.

    Would anyone know where i am doing it wrong.

    S 1 Reply Last reply Mar 12, 2024, 4:15 PM Reply Quote 0
    • S
      SteveITS Galactic Empire @anishkgt
      last edited by Mar 12, 2024, 4:15 PM

      @anishkgt Are you trying to isolate port 2, as in make it a separate port, or to have the VLAN work on any port? I don't know that there's a way to make a VLAN work on just one port of the switch, I suspect you need to add it to the switch (also).

      similar question: https://forum.netgate.com/topic/186576/vlans-on-netgate-2100

      Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
      When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
      Upvote 👍 helpful posts!

      A 1 Reply Last reply Mar 12, 2024, 4:20 PM Reply Quote 0
      • A
        anishkgt @SteveITS
        last edited by anishkgt Mar 12, 2024, 4:22 PM Mar 12, 2024, 4:20 PM

        @SteveITS I did see that post yesterday when I came here to post. Turns out that was not what I was looking for. I am planning to Isolate it to have it only for wireless clients.

        S 1 Reply Last reply Mar 12, 2024, 4:38 PM Reply Quote 0
        • S
          SteveITS Galactic Empire @anishkgt
          last edited by Mar 12, 2024, 4:38 PM

          @anishkgt OK, then if you go through the steps of:
          https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/configuring-the-switch-ports.html
          ...it will be a separate port. No VLAN configuration is necessary for the wireless clients or APs, since the 2100 handles that as the packets arrive over that cable. That example is port 4 but you can use any port and VLAN number.

          Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
          When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
          Upvote 👍 helpful posts!

          1 Reply Last reply Reply Quote 1
          4 out of 4
          • First post
            4/4
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            This community forum collects and processes your personal information.
            consent.not_received