pfSense

related issue - #6370 (duplicate?)

Viktor Gurov wrote in #note-4:

related issue - #6370 (duplicate?)

It's possibly related but I wouldn't say it's the same thing at a glance. This particular issue affects refreshing the config even without failover/failback.

If someone can still reproduce that other issue, try it on a current snapshot with this fix in place. If it does work, the old issue can be cross-referenced here and closed.

Jim Pingle wrote in #note-5:

Viktor Gurov wrote in #note-4:

related issue - #6370 (duplicate?)

It's possibly related but I wouldn't say it's the same thing at a glance. This particular issue affects refreshing the config even without failover/failback.

If someone can still reproduce that other issue, try it on a current snapshot with this fix in place. If it does work, the old issue can be cross-referenced here and closed.

I reported this through Netgate support yesterday. Just to get it crystal clear; this also affects pfSense when having an interface configured in P1, a gateway group is not mandatory. (Jim, you eventually meant that with "even without failover/failback").

There are other cases in which the tunnel may not get re-established ( e.g. #12169 ) which are separate from this issue. This fix should - for example - address the case in which the IP changes for an interface in a gateway group bound to IPsec.

If you can reproduce the issue without the use of gateway groups, please collect the logs including the time when the issue happened and follow up with support.