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

    Site to Site VPN - Cannot ping remote lan

    Scheduled Pinned Locked Moved IPsec
    5 Posts 2 Posters 787 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.
    • N
      nappy_d
      last edited by nappy_d

      I have two pfsense 2.4.4 appliances setup.

      They have been working great. We now want to setup a site to site VPN and this has been configured however we are not able to reach any devices on the remote sides once the VPN is up.

      Here are my configurations in hopes that someone can see anything that was missed.

      0_1539098477568_Screen Shot 2018-10-09 at 11.19.16 AM.png

      0_1539098492636_Screen Shot 2018-10-09 at 11.18.42 AM.png

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

        What does status IPsec show? Are the tunnels coming up?

        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
        • N
          nappy_d
          last edited by

          The tunnels are up and connected.

          I have recreated them with no resolution.

          I am unable to route or ping them.

          0_1539112367040_Screen Shot 2018-10-09 at 3.08.27 PM.png

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

            Yeah, that looks fine. You intended both of those to be /32? You had /24s in the other examples.

            Are the proper rules on the Firewall > Rules, IPsec tabs in place?

            Are there local firewalls on the target hosts that might be blocking the "foreign" traffic?

            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 1
            • N
              nappy_d
              last edited by

              DOH!!

              Thanks for the second pair of eyes. It was the remote network was set to address instead of network.

              Changed that and all is working well. :)

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