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

    IPSec in 2.4.1 and 2.4.2

    Scheduled Pinned Locked Moved IPsec
    1 Posts 1 Posters 605 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.
    • Z
      Zaphon
      last edited by

      I upgraded a few boxes from 2.4.0 to 2.4.1 last night, and when I checked this morning their IPSec tunnels weren't functioning.  I read some issues that it was purely a display issue and that it was fixed in 2.4.2, so I upgraded to the latest development snapshot.  I can confirm that the Status screen for IPSec is now properly working again, however I'm still having the same issue that no traffic is moving from my LAN to the REMOTE LAN via IPSec.

      What I found odd is that I can logon to 1 pfSense box and from it using ping -S hit the other pfSense box.  So it's looking like for whatever reason the tunnel's are up, the routers can ping each other, but traffic from the subnets is not being routed across the IPsec links.  I've triple checked all the phase 2 entries, and nothing is wrong with them.

      Any ideas here?

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