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

    PFSENSE 2.4 and Cisco 3560 Multiple VLANs Routing

    Scheduled Pinned Locked Moved Routing and Multi WAN
    routingciscovlannat
    1 Posts 1 Posters 492 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.
    • K
      krisarmstrong
      last edited by

      I have the following setup:

      Cisco 3560-X Cisco Switch with IP Routing enabled.
      VLAN 1: 10.0.1.5/24
      VLAN 2: 10.0.2.1/24
      VLAN 3: 10.0.3.1/24
      ip route

      Relevant Section of switch Config:

      ip routing
      
      interface Vlan1
       description DEFAULT VLAN 1 - Managment
       ip address 10.0.1.5 255.255.255.0
      end
      
      interface Vlan2
       description WIRELESS VLAN 2 - Data
       ip address 10.0.2.1 255.255.255.0
      end
      
      interface Vlan3
       description WIRELESS VLAN 3 - Data
       ip address 10.0.3.1 255.255.255.0
      end
      
      ip route 0.0.0.0 0.0.0.0 10.0.1.1
      

      PFSENSE LAN Interface: 10.0.1.1

      From the switch I'm able to ping devices on VLAN 1, 2 and 3 which is expected behavior, however, devices on VLAN 2 and 3 are unable to ping devices on VLAN 1 which makes sense, as the PFSENSE box is the gateway for that VLAN and there are no routs on the PFSENSE box and of course VLAN 2 and 3 cannot get outbound.

      So my questions are:
      1.) What steps need to take place on the PFSENSE box so all VLANs can get outbound and communicate with each other.
      2.) The other piece is I would prefer all VLAN routing to occur on the Cisco 3560 for performance that said I know VLAN 1 won't be that way based on current config.

      I think the perfect world scenario would be to have PFSense on its own SUBNET / VLAN just for internet connectivity the problem with that is if I do that then I don't get IPv6 addresses to any other devices except the VLAN PFSENSE is in. And for my purposes, I need to see IPV6 at least on VLAN 1. Which with the current setup is working as expected. Ideally again in a perfect world, I would get IPV6 on all VLANs.

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