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

    [Resolved ] Vlan not working

    Scheduled Pinned Locked Moved General pfSense Questions
    26 Posts 4 Posters 5.4k 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.
    • DerelictD
      Derelict LAYER 8 Netgate
      last edited by

      That all looks better.

      Make a trunk port with allowed vlan 60 and patch it to em0

      Make an access port on vlan 60 and plug in any laptop set to DHCP.

      Wait for spanning-tree to do its thing and you should be on 192.168.60.0/24

      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
      • S
        Snailkhan
        last edited by

        @Derelict:

        That all looks better.

        Make a trunk port with allowed vlan 60 and patch it to em0

        Make an access port on vlan 60 and plug in any laptop set to DHCP.

        Wait for spanning-tree to do its thing and you should be on 192.168.60.0/24

        i did a reboot and now its working when directly connected to lan port..
        but it doesnt works when an ap is inserted in between pfsense and server.
        the ap is tplink wifirouter (tl-wr740n) using ddwrt in ap mode . (wan port disabled. routing disabled. dhcp relaying enabled )..

        it seems that it doesnt supports vlans as its atheros based chip in this ap.

        however my issue is resolved.

        tried with cisco 3550 was able to trunk pfsense lan to cisco port 1 and another trunk from cisco port 7 to server.

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

          Good to hear.

          What did you reboot?

          I add and remove VLANs all the time on 2.1.5 and 2.2.6 I never have to reboot pfSense to make it work.

          If it works on two tagged ports it should work directly connected, as long as you don't need a crossover cable (or use a crossover cable).

          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
          • S
            Snailkhan
            last edited by

            @Derelict:

            Good to hear.

            What did you reboot?

            I add and remove VLANs all the time on 2.1.5 and 2.2.6 I never have to reboot pfSense to make it work.

            If it works on two tagged ports it should work directly connected, as long as you don't need a crossover cable (or use a crossover cable).

            I rebooted pfsense.
            And magically both vlan interfaces on my pc obtained ip.
            Now it's doing vlaning properly.

            1 Reply Last reply Reply Quote 0
            • R
              rudelerius
              last edited by

              but it doesnt works when an ap is inserted in between pfsense and server.
              the ap is tplink wifirouter (tl-wr740n) using ddwrt in ap mode . (wan port disabled. routing disabled. dhcp relaying enabled )..

              It should work fine if you connect the AP to a port on your switch that is properly configured for the vlan that you wish the wireless clients to be in.

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

                I think he's saying he's trying to use the AP as a switch. You would have to make the switch ports tagged ports on the AP for that to work.

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