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

    [Solved]Getting confused with routing vlans

    Scheduled Pinned Locked Moved Routing and Multi WAN
    3 Posts 2 Posters 693 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.
    • B
      BaNZ
      last edited by

      I've configured a couple of vlans within pfsense. My switch is a linksys sfe2000p and I've been following the guide on https://www.highlnk.com/2014/06/configuring-vlans-on-pfsense/

      On the switch I set port E1 to be access port and untag VLAN ID 10.
      I get a dhcp address but I cannot ping the vlan gw or get out the internet.

      On port 2 where it is left as trunk port and vlan 10 tagged.
      I get dhcp address, I can ping the vlan gw and I can get out the internet.
      I get the wrong range of dhcp address but vlan gw and internet works. The IP I'm getting is the pfsense LAN interface that is connected to the switch and not the VLAN 10 range.

      I'm trunking all the vlans on port 24 already. I thought I'm supposed to be configuring the ports as access ports on E1?  My pc is plugged into E1 and I only want it allow access to vlan id 10 and not the others. Am I not doing it correctly?
      1.png
      2.png
      1.png_thumb
      2.png_thumb

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

        If you are getting DHCP it's not the VLANs.  You have good layer 2.

        You have firewall rule and/or NAT issues.  See the other thread.

        Note that rules permitting DHCP traffic on a pfSense interface are automatically added to interfaces with a DHCP server defined.  That's probably why DHCP is working but nothing else is.

        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
        • B
          BaNZ
          last edited by

          @Derelict:

          You have firewall rule and/or NAT issues.  See the other thread.

          Note that rules permitting DHCP traffic on a pfSense interface are automatically added to interfaces with a DHCP server defined.  That's probably why DHCP is working but nothing else is.

          You're right. Turns out my firewall rule set only to allow any TCP so I was actually able to access the pfsense web configurator but nothing else.

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