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

    Cannot connect/ping from internal to pfSense and vice versa

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    22 Posts 3 Posters 2.3k 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.
    • I
      icq9988 @johnpoz
      last edited by

      @johnpoz Sorry I missed that details. I will stop by tonight to install another Cisco Aeronet WAP, will try for that.

      Again appreciate for your help on this :)

      M 1 Reply Last reply Reply Quote 0
      • M
        marvosa @icq9988
        last edited by

        @icq9988 Yes, you will need an any/any (or defined alias/any) on the LAN interface assuming that's where 10.30.54.1 is addressed.

        If the other VLANs still aren't communicating once you've added the firewall rule(s) to the LAN, post the running-config, "sh ip route" from the switch, and the routing table from PFsense.

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