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

    IPSec Routing is not working after upgrading pfsense from 2.4.4 to 2.6.0

    Scheduled Pinned Locked Moved IPsec
    2 Posts 1 Posters 827 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.
    • T
      Tekchand
      last edited by

      Hello Team,
      We are using IPSEC tunnel for connectivity between two different region of digitalocean cloud.

      Earlier we are using pfsense 2.4.4 and everything was working fine.
      Now we have upgraded our pfsense version to 2.6.0 and its seems that routing is not working.

      I am trying to explain the scnerio which may be helpful to understand the problem:

      Region 1: We have one pfsense i.e (pfsense1) with IPSec Tunnel.
      Region 2: We have one pfsense i.e (pfsense2) with IPSec Tunnel.

      With version 2.4.4 when we add pfsense 1 as source in firewall rule for Region 1 server then traffic can reach to Region 1 server from Region 2 server and vice versa.

      But after upgrading to 2.6.0 its not working.

      We have one Jump Box (Bastion Host) in Region 1. Earlier for SSH we allowed only pfsense2 as source for SSH for Region 2 server and SSH was working fine.

      But now we need to add Jump Box as source for SSH for Region 2 server only then we can SSH Region 2 server.

      We have all the route in place on both the pfsense.

      Can you please help us?

      Thank You

      1 Reply Last reply Reply Quote 0
      • T
        Tekchand
        last edited by

        Hello Team,

        Can you please help us on above issue?

        Thank You

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