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

    IPsec Tunnel Woes

    Scheduled Pinned Locked Moved IPsec
    3 Posts 2 Posters 201 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.
    • P
      pharceface
      last edited by pharceface

      Greetings, I am working to have both sides of an tunnel ping one another. Both the phase 1 and phase 2 establish just fine, and I can even ping devices on the other end from each firewall's diagnostic menu. Outside of the firewalls ping menus nothing gets through (ie. ping from Windows terminal). Side A is a pfsense firewall with LAN 10.10.4.X and side B is a SonicWall 10.10.12.X From Side A if I go to command prompt (from within pfSense) and run ping -S 10.10.4.XX 10.10.12.XX I get the response ping: bind: Can't assign requested address
      But if I ping from Side A local subnet to an IP address on Side B I get a response. I'm not sure where I need to be looking for to figure out what's happening here.

      V P 2 Replies Last reply Reply Quote 0
      • P
        pharceface @pharceface
        last edited by

        @pharceface I got it worked out, both devices needed a port open to communicate.

        1 Reply Last reply Reply Quote 0
        • V
          viragomann @pharceface
          last edited by

          @pharceface
          You want to access the remote site from pfSense itself or access a service on pfSense from remote?
          Then you'll need a Static Route Workaround as explained in the docs.

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