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

    Mysterious (to me) vlan routing

    Scheduled Pinned Locked Moved Routing and Multi WAN
    4 Posts 2 Posters 681 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.
    • D Offline
      dilophosaur
      last edited by

      Hey all, I'm fairly new to pfsense so please bear with me. I've simulated a network environment in GNS3 using several pfsense routers. I've created routing rules to facilitate communication between my networks and it works great.
      Recently I've added a vlan and it also seems to work just fine. I was very surprised however, when I tried to ping a host on my vlan from another host across the wan and got a response. I haven't created any routing rules that specify how to reach my vlan (which is a different network address). How is this happening? Is this normal?

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

        Impossible to say with the information provided.

        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
        • D Offline
          dilophosaur
          last edited by

          Should I dump my entire configuration? What would be the most effective way to present it for you?

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

            No.

            Maybe look around the forum to see what information is necessary.  Look at the diagram in my sig for the information necessary.

            Interface addresses, netmasks, and gateways, firewall rules, etc.

            A diagram is always best.

            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.