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

    Pfsense new install topology

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    20 Posts 6 Posters 4.5k 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.
    • johnpozJ Offline
      johnpoz LAYER 8 Global Moderator
      last edited by

      "The APs are Unifi UAP-LR which "do support" VLAN's but the more I read into them it would appear you're supposed to leave them untagged and just use the VLAN option on their controller software to set the VLAN tagging up"

      You would assign different vlans to your different SSID either via the controller directly or via dynamically assigned vlans and radius, etc.

      End devices normally do not need to be tagged, think your confused about how a device in 1 vlan accesses devices in another vlan.  To access another vlan from a device in vlan A, the device would go through the router/firewall to access this other network.

      Only time you would need to tag vlans to an end device like a printer or a pc would be if you were going to send it traffic from multiple vlans at the same time and it had to sort out what vlan the traffic was in based up on the tag.  You do this on a switch, AP, router etc..  Where traffic from multiple vlans is entering the device via an "uplink"..

      The management IP on a unifi AP has to be untagged, it can be in any vlan you want but it is untagged.  It can place traffic from its different wireless networks (ssid) to different vlans via tagging yes.  But its management interface would be on an untagged vlan.

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 24.11 | Lab VMs 2.8, 24.11

      1 Reply Last reply Reply Quote 0
      • S Offline
        smithr99
        last edited by

        thanks johnpoz. Im a little clearer now (I was panicking that i'd have to use VLAN 1 for my AP's which kind of went against what I'm aiming at here!). Just so I'm clear does my topology diagram look ok to you? (albeit removing the vast majority of the "T" tags)

        cheers

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

          The Ubiquiti devices really like to be managed on the untagged VLAN on the port they are connected to. In fact I'm pretty sure Ubiquitis do not support anything but the untagged VLAN as the management VLAN. Seems like I remember trying it before and the APs kept reverting to untagged. I think the capability to even try to set a management VLAN there has been removed.

          That untagged VLAN does NOT have to be VLAN 1, however. It can be whatever you want. Just needs to be untagged (The PVID) on the switch port(s) going to the AP(s). So your management VLAN SSID should be untagged (if you have one) and other SSIDs should be tagged with a VLAN.

          ETA: (basically just repeating what johnpoz already said but I'll leave it. derp.)

          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 Offline
            smithr99
            last edited by

            Thanks for all the help so far. I'm aware that I dont want to turn this thread into a Networking 101 session but I promise this is all leading to a good understanding of pfSense and how best to implement it in my network (!)

            Ive done another diagram (or 3) attached which shows what I THINK should be the case for tagging and PVIDs on my Netgear switches. I've trunked all of them together on ports 23/24 and 28 (all GBit ports on these) and have tagged ALL VLANs on those ports with NO PVID.

            I've then defaulted to using UNTAGGED on the relevant VLAN for each port that has a device on it and also set the PVID to the relevant VLAN for each of these. This may be way off but please be gentle as this is all new to me today!

            One question I do have is should I delete the PVID for all the unused ports (they're currently all set to 1 which I dont want)

            screenshots attached - if you fancy correcting me, the Google sheets copy is here…https://docs.google.com/spreadsheets/d/1-W4Mb7t5SEu1RDRopeu9z6CAIpEUnBB6azhGiZyO2qg/edit?usp=sharing

            switch2.PNG_thumb
            switch2.PNG
            switch1.PNG_thumb
            switch1.PNG
            switch3.PNG
            switch3.PNG_thumb

            1 Reply Last reply Reply Quote 0
            • johnpozJ Offline
              johnpoz LAYER 8 Global Moderator
              last edited by

              Your last picture where you have untagged multiple vlans 20, 50 and 60.. that is borked.. You don't run multiple vlans same connection untagged.  So device connected to port 1 for example.  He would see untagged traffic all three of those vlans..

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 24.11 | Lab VMs 2.8, 24.11

              1 Reply Last reply Reply Quote 0
              • S Offline
                smithr99
                last edited by

                @johnpoz:

                Your last picture where you have untagged multiple vlans 20, 50 and 60.. that is borked.. You don't run multiple vlans same connection untagged.  So device connected to port 1 for example.  He would see untagged traffic all three of those vlans..

                Those ports are used to connect my unifi APs so in theory I need them to access vlans 20 50 and 60? Unless you mean I just leave them on 20 only as 50 and 60 will be managed by the APs themselves?

                1 Reply Last reply Reply Quote 0
                • P Offline
                  phil.davis
                  last edited by

                  On a switch port that goes to a Unifi AP, you would make the VLAN that you want to use to mange the AP be untagged - those packets will then be sent as ordinary ethernet frames to the AP. Other VLANs that you want to use for carrying the traffic for each WiFi SSID you make tagged. Then the switch sends a tagged ethernet frame for packets in that VLAN. So the Unifi AP can listen for (and send) packets to/from each WiFi SSID from/to the corresponding VLAN.
                  This was the first thing that came up in my search, and shows what to do:
                  https://help.ubnt.com/hc/en-us/articles/219654087-UniFi-Using-VLANs-with-UniFi-Wireless-Routing-Switching-Hardware

                  As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                  If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                  1 Reply Last reply Reply Quote 0
                  • johnpozJ Offline
                    johnpoz LAYER 8 Global Moderator
                    last edited by

                    ^ exactly…

                    So what "vlan" is the management IP of your AP it, is it 20?  Then 20 would be untagged.. And normally that would be the PVID of that port..  Then 50 and 60 would be tagged..

                    I can never think of any sort of setup where you would run more than 1 vlan untagged on the same port.. Other than maybe a span port that you were sniffing traffic on?

                    An intelligent man is sometimes forced to be drunk to spend time with his fools
                    If you get confused: Listen to the Music Play
                    Please don't Chat/PM me for help, unless mod related
                    SG-4860 24.11 | Lab VMs 2.8, 24.11

                    1 Reply Last reply Reply Quote 0
                    • S Offline
                      smithr99
                      last edited by

                      @johnpoz:

                      ^ exactly…

                      So what "vlan" is the management IP of your AP it, is it 20?  Then 20 would be untagged.. And normally that would be the PVID of that port..  Then 50 and 60 would be tagged..

                      I can never think of any sort of setup where you would run more than 1 vlan untagged on the same port.. Other than maybe a span port that you were sniffing traffic on?

                      Thanks both,
                      Yes APs will be managed from vlan20 and there will be SSIds setup on each for access to 30 50 and 60. I've made the necessary changes to the Google spreadsheet (link above) if you wouldn't mind checking? (sorry for asking all this!)

                      1 Reply Last reply Reply Quote 0
                      • johnpozJ Offline
                        johnpoz LAYER 8 Global Moderator
                        last edited by

                        what did you change - I still see multiple untagged vlans.. on switch 3 on the same port.

                        An intelligent man is sometimes forced to be drunk to spend time with his fools
                        If you get confused: Listen to the Music Play
                        Please don't Chat/PM me for help, unless mod related
                        SG-4860 24.11 | Lab VMs 2.8, 24.11

                        1 Reply Last reply Reply Quote 0
                        • S Offline
                          smithr99
                          last edited by

                          @johnpoz:

                          what did you change - I still see multiple untagged vlans.. on switch 3 on the same port.

                          not sure why (maybe google drive didnt update?! Anyway, ive attached screens…

                          1.PNG
                          1.PNG_thumb
                          2.PNG
                          2.PNG_thumb
                          3.PNG
                          3.PNG_thumb

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

                            Netgear switches are complete and utter piles of crap. See those ports (01-06) with both untagged and tagged VLANs on 10.0.10.12? Are those your Ubiquitis?

                            Try also manually setting the PVID to 20 on those ports. Not having the PVID shown there makes me think that might be your issue.

                            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 Offline
                              smithr99
                              last edited by

                              @Derelict:

                              Netgear switches are complete and utter piles of crap.

                              I would concur!

                              See those ports (01-06) with both untagged and tagged VLANs on 10.0.10.12? Are those your Ubiquitis?

                              Try also manually setting the PVID to 20 on those ports. Not having the PVID shown there makes me think that might be your issue.

                              thanks, will give that a go..

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