Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    vlans stop working after using new hardware

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    6 Posts 4 Posters 246 Views 5 Watching
    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.
    • M Offline
      moosport
      last edited by moosport

      After replacing existing hardware which vlans were working. With new hardware, vlans are broken.

      config was restore after new hardware was plugged in. interfaces were reassigned the new WAN and LAN.

      Devices plugged in are handed the correct IPs for the vlan tagged at the switch.
      But it cannot ping devices on the same vlan. or the gateway.

      There are no change to the firewall rules. It should not be affected by interface change.

      Do I need to recreate vlans in pfsense?

      After some research, the following changes were made to the switch

      1. Change port Untagged VLAN to 50 both ports.
      2. Change VLAN Membership - By VLAN participation to excluded for both ports.

      Now devices can ping each other. But ping to pfsense still do not work.

      JKnottJ SteveITSS 2 Replies Last reply Reply Quote 0
      • JKnottJ Offline
        JKnott @moosport
        last edited by

        @moosport

        Wireshark is your friend for this sort of problem, to see what's killing the VLAN.

        You don't say what was replaced so anything I say might refer to the wrong hardware. However, first off, you have to create the VLANs in pfSense if they aren't there already. Then, the switch must be configured for the VLANs. Based on your very limited description, my guess is the switch has not been configured for VLANs.

        PfSense running on Qotom mini PC
        i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel 1 Gb Ethernet ports.
        UniFi AC-Lite access point

        I haven't lost my mind. It's around here...somewhere...

        M 1 Reply Last reply Reply Quote 0
        • M Offline
          moosport @JKnott
          last edited by

          @JKnott

          Old router m920q was replaced with X11SDV-4C-TP8F.

          I had to recreate the interfaces for vlans after backup was restored in addition to remapping WAN and LAN.

          Pfsense->aruba 1930->unifi16->unifi AP

          These setup works prior to replacement.
          To troubleshoot, 2 ports on Aruba were set to guest vlan. Uplink port is trunk to allow all vlans.

          1 Reply Last reply Reply Quote 0
          • U Offline
            Uglybrian
            last edited by

            I had similar issues when I switched from my A1 SRM – 2558 to Netgate 4200. There were inconsistencies, I tried to correct a few to get the basics going. But, I just ended up doing a factory reset on the 4200.
            I’m thinking if it’s not the exact hardware on the restore from to the restore to, things go a little sideways.

            M 1 Reply Last reply Reply Quote 0
            • M Offline
              moosport @Uglybrian
              last edited by

              @Uglybrian
              I was having issues with the restore with the webgui locking up.

              So I manually renamed the interfaces in the xml file before restoring.

              Good to know. I’ll have to take some screenshots to reconfigure after reset.

              1 Reply Last reply Reply Quote 0
              • SteveITSS Offline
                SteveITS Rebel Alliance @moosport
                last edited by

                @moosport said in vlans stop working after using new hardware:

                Devices plugged in are handed the correct IPs for the vlan tagged at the switch.
                But it cannot ping devices on the same vlan. or the gateway.

                Devices on the same network do not communicate through the gateway/pfSense.

                Subnet mask correct?

                To upgrade, select your branch in System/Update/Update Settings. When upgrading, allow 10-15 minutes to reboot, or more depending on packages, CPU, and/or disk speed.
                Only install packages for your version of pfSense.
                Upvote 👍 helpful posts!

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.
                Privacy Policy · Cookie Policy