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

    Can't reach LAN address from VLAN

    Scheduled Pinned Locked Moved Firewalling
    3 Posts 2 Posters 507 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.
    • E Offline
      Elegant
      last edited by

      Hi guys, I'm currently trying to access my management interface for my VMs that is currently not on a VLAN. I'm am trying to do this from a device on VLAN 10 which has been given permission to everything on the network. Unfortunately, I can only reach the gateway of the LAN anbd my management interface. I can ping my mangement interface from pfSense so I know it is reachable just I need to figure out what I'm doing wrong here.
      ![VLAN 10 Rules.png](/public/imported_attachments/1/VLAN 10 Rules.png)
      ![VLAN 10 Rules.png_thumb](/public/imported_attachments/1/VLAN 10 Rules.png_thumb)

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

        Everything on ADMIN10 is being policy routed out WAN_PPPOE. You need to bypass policy routing above that rule for the local networks you are trying to access like you're doing with the VPN networks.

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

        Your Full access to network rule does nothing because the rule above it matches the same traffic so it will be controlling instead.

        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
        • E Offline
          Elegant
          last edited by

          Good call! I moved the bottom rule to the top then changed the destination to 10.0.0.0/16. This should make it so I can access the network.

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