Bug #2303
SPD on secondary not cleared after config sync
| Status: | Feedback | Start date: | 03/20/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 100% |
|
| Category: | Config sync | |||
| Target version: | 2.1 | |||
| Affected version: | All | Affected Architecture: |
Description
When IPsec is disabled on the primary, it syncs over and disables it on the secondary, but it leaves the SPD in place. The SPD and SAD have to be cleared on the secondary in such situations, same as they are on the primary.
Associated revisions
Make sure we create / delete SPDs and SADs on secondary node when it changes on primary. Fixes #2303
History
#1
Updated by Erick Tyack 10 months ago
pfSense is our primary gateway running behind a telco provided MPLS network. In the event we lose a connection at one of our remote locations, we bring an IPSec VPN up on a backup Internet connection. Once the MPLS network is restored, we tear down the IPSec VPN tunnel. Leaving the SPD in place causes a headache with routing until SPD's are manually deleted. Is is possible to bump this bug up in priority? Thanks.
#2
Updated by Renato Botelho 3 months ago
- Target version set to 2.1
#3
Updated by Renato Botelho 3 months ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset d026178fa695f607f3b490978a9f4113fa7b111d.