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

    VLAN suddenly stopped working

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    21 Posts 3 Posters 1.8k 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.
    • J
      Jarhead @Brian Smit
      last edited by

      @brian-smit Ok, so you need a trunk going to the AP as well. Same as pfSense port, native 1, tagged 2.

      B 1 Reply Last reply Reply Quote 0
      • B
        Brian Smit @Jarhead
        last edited by

        @jarhead

        Yes indeed, i will change the settings tomorrow and keep you informed !

        Thank you for the help!

        N 1 Reply Last reply Reply Quote 0
        • N
          NRgia @Brian Smit
          last edited by

          @brian-smit From the manual: "802.1Q VLAN Trunk Ports for APs
          The trunk ports are the ones through which Aerohive APs connect to the wired network. They support 802.1Q tagging and must allow all the VLANs to which the APs assign user traffic, the management VLAN for the APs, and the native (untagged) VLAN. "
          You can find more here: https://docs.aerohive.com/330000/docs/guides/Aerohive-Switch-Deployment-Essentials.pdf under "Configuring a Network Policy" section.

          B 1 Reply Last reply Reply Quote 1
          • B
            Brian Smit @NRgia
            last edited by

            @nrgia

            Thank You ! I will go through the steps tomorrow. A small change has been made and that had big consequences (and i am overseeing it)

            1 Reply Last reply Reply Quote 0
            • B
              Brian Smit
              last edited by Brian Smit

              is there someone maybe with tips where to find the problem ?

              I wonder if (DHCP) requests are being received by PFsense

              J 1 Reply Last reply Reply Quote 0
              • J
                Jarhead @Brian Smit
                last edited by

                @brian-smit Did you tag the vlan on the correct port? Do you have the correct vlan untagged on the ports you need?

                Post pictures of pfSense and switch configs

                B 1 Reply Last reply Reply Quote 1
                • B
                  Brian Smit @Jarhead
                  last edited by Brian Smit

                  @jarhead said in VLAN suddenly stopped working:

                  Did you tag the vlan on the correct port? Do you have the correct vlan untagged on the ports you need?

                  Yes - i double checked this.

                  Pictures of my PFsense config:

                  Interface Assignments:
                  9e94e78f-73e1-4df8-9306-c93a11284b6b-image.png

                  Interfaces - VLANs:
                  fafd4ef5-f4f7-4495-8420-d72f3539c912-image.png

                  Interfaces - Guests (igb1.2)
                  4326ae10-51bd-4bce-b9bd-91b1034b9486-image.png

                  Services - DHCP Server - Guests
                  f9e0d4f5-b024-4e14-980b-15103cfd9807-image.png

                  Switch port configuration:

                  5c8a9f17-780d-42c1-bb87-d31c02fa09eb-image.png

                  fb7a09d2-1adc-49c0-9c61-fb0eea360127-image.png

                  2fc6bbc9-087f-417f-b286-27fb536f77dc-image.png

                  J 1 Reply Last reply Reply Quote 0
                  • J
                    Jarhead @Brian Smit
                    last edited by

                    @brian-smit So I'll ask again... Why are you allowing all vlans on all ports?

                    Set it up correctly. All ports do not nned to be trunks, it will still work if correct vlans are on them but not needed.

                    Set up untagged ports which conect to clients.
                    Set up tagged ports that connect to pfSense and AP's.
                    These ports should only allow the vlan's needed on each.

                    B 2 Replies Last reply Reply Quote 1
                    • B
                      Brian Smit @Jarhead
                      last edited by

                      @jarhead

                      I'm going to change it and will change the other ports indeed into access ports.

                      I'll report back :-)

                      Above switch config could be the whole issue?

                      1 Reply Last reply Reply Quote 0
                      • B
                        Brian Smit @Jarhead
                        last edited by Brian Smit

                        @jarhead

                        short update as promised:

                        Changing the configuration of the switch and only allowing the VLANs that we actually use (in stead of "ALL") solved the problem!

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