Hi, I checked with strongswan 5.2.0, and the behavior remains the same.
So, is this an intended behavior? - Divya On Thu, Jul 24, 2014 at 1:53 PM, Martin Willi <[email protected]> wrote: > Hi, > >> I have a query regarding the priority assigned to kernel policies. > >> I am running IKEv2 (strongSwan 4.4.0) on DUT. > > That release is now more than four years old. A lot has changed since > then, and I really don't know how the policy priorities have been > handled back then. > >> 1. Configure tunnel A. >> 2. Start traffic, so that CHILD_SAs are established. >> 3. Configure tunnel B and send SIGHUP to starter. > > There have been some changes to trap policy priorities in the latest > 5.2.0 release. You should try that, not unlikely that this has been > fixed. > > Regards > Martin > _______________________________________________ Users mailing list [email protected] https://lists.strongswan.org/mailman/listinfo/users
