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

    New VLAN won't route to other VLANs

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    6 Posts 5 Posters 973 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.
    • F
      fescorick
      last edited by

      I an working on adding a VLAN to our network for some new wireless devices. I've setup the VLAN on our Netgear switches and also in pfSense. I've added a firewall rule of any>any to test connectivity but when I ping between them, I'm not getting a reply. The devices are routing to the internet properly. I feel like i'm missing something easy somewhere but it's driving me crazy! I've searched the forums and haven't found the smoking gun yet.

      Config is as follows:

      VLAN 4: Internal (192.168.53.0/24)
      VLAN 5: Tablets (192.168.5.0/24)

      I've checked the logs and it says the packets are routing, but I'm not seeing them on wireshark on the target PC.

      Any help or pointers would be much appreciated!

      Thank you all in advance for your help!

      1 Reply Last reply Reply Quote 0
      • V
        veldthui
        last edited by

        Maybe the switches are not set up for the VLans correctly? I know I had issues with my DLink switch until I got it right. Same symptoms.

        F 1 Reply Last reply Reply Quote 0
        • F
          fescorick @veldthui
          last edited by fescorick

          @veldthui THANKS for the quick reply!

          From any computer on the .53.0 subnet, I can ping 192.168.5.1, but the devices on the 5.0 subnet can't ping 192.168.53.1.

          I was heavily leaning down the VLAN setup on the switches, but I was assuming that since the packets can reach the pfSense router, the VLAN would be correct and it's a routing issue. I can dig deeper into the switches if that would help.

          Thanks again!

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

            Sounds like firewall rules on the 192.168.5.0 interface.

            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
            • J
              JonathanSalva
              last edited by

              Hi! Mr. fescorick
              Could be the common problem on NIC installed
              https://www.netgate.com/docs/pfsense/book/hardware/index.html

              Test changing the NIC to a Intel PRO

              :)

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

                Did you put a gateway on your vlan 5 rules? This is common mistake where users set a gateway on the rule, this forces traffic out that gateway vs allowing pfsense to use it routing table.

                Post up your rule(s) you put on vlan 5 interface

                Blocking rfc1918 on the interface have seen as well.

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