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

    Second VLAN as subnet

    Scheduled Pinned Locked Moved Routing and Multi WAN
    3 Posts 3 Posters 864 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 Offline
      jpinder70
      last edited by

      Greetings -

      I'm doing a test with pfsense but I'm having a little issue with routing or firewall.

      Scenario:

      Network Layout
      2 WAN + 1 LAN + 1 VLAN(second subnet)

      IP WAN1: 1.1.1.1
      IP WAN2: 2.2.2.2

      IP LAN: 10.10.10.1/24

      IP VLAN : 192.168.80.1/24

      • Workstations behind LAN can ping 192.168.80.1 pfsense IP on VLAN

      • Workstations behind VLAN can ping 10.10.10.1 pfsense IP LAN

      • Workstations behind VLAN can ping any workstation on the LAN

      I opened firewall to allow all protocols on VLAN

      Here's the issue i'm having. Workstations on LAN cannot ping any workstations or devices on VLAN subnet

      What am I missing?

      Thanks in advance

      1 Reply Last reply Reply Quote 0
      • T Offline
        tim.mcmanus
        last edited by

        Did you have a similar "allow any" on the LAN firewall too?

        I have explicitly set up a rule that says "any from LAN net to LAN2 net" and the opposite on the other LAN. In your case it would be the VLAN.

        Try creating an explicitly net to net rule on the LAN and VLAN to see if that works.

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

          You are probably telling LAN to send traffic to your VLAN out your Multi-WAN group.

          https://doc.pfsense.org/index.php/What_is_policy_routing

          https://doc.pfsense.org/index.php/Bypassing_Policy_Routing

          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.