2.3.1 / site-to-site: routing/pf issue after upgrade from 2.2.6
-
Darn, I think I finally found the culprit: I had an old IPSec config on those boxes (preferred VPN solution but never got it work reliably) which was inactive but not disabled. It seems as if this messes up some internal routing (not reflected by the routing table). It also seems that this is a regression in 2.3.? since 2.2.6 still doesn't have this problem! IIRC, the enable/disable implementation of IPSec changed in 2.3 so that would explain it.
That was a mean one…
Cheers
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.