New commits:
commit fbb48cf081ecf57659e56cd627310a18d2620a60
Merge: 6341a19984 77042b6574
Author: Andrew Cagney <[email protected]>
Date: Tue Feb 17 09:39:50 2026 -0500
Merge updown: add EXPERIMENTAL async option
When enabled, on the initiatl IKE responder (aka server)
it invokes updown once with:
PLUTO_VERB=prepare-route-up
PLUTO_{MY,PEER}_...=first SPD (which is clearly wrong)
and then lets it run asynchronously (it doesn't even sync
it with the connection, again clearly wrong).
This is sufficient for playing with the updown script
and figuring out what to really do.
Close #2621 when updown-flags=async, run updown in background
commit 77042b6574ac0cf30e935e9340c97d9498058b2e
Author: Andrew Cagney <[email protected]>
Date: Tue Feb 17 09:38:41 2026 -0500
testing: expect updown-flags=noasync
since that's the default
commit 742f0b787378bccaea7bb00b6d9605bb973145d6
Author: Andrew Cagney <[email protected]>
Date: Mon Feb 16 22:32:19 2026 -0500
updown: when updown-flags=async, pass first SPD to updown
(which is less broken then dumping core)
commit 20586bfc4ed14540bd021008e74b4523f9b9ca48
Author: Andrew Cagney <[email protected]>
Date: Mon Feb 16 22:31:32 2026 -0500
documentation: updown-flags=async
commit d4931ca0468e382bb14005035f120eee4a86ca5e
Author: Andrew Cagney <[email protected]>
Date: Mon Feb 16 18:47:16 2026 -0500
updown: add updown-flags=async
_______________________________________________
Swan-commit mailing list -- [email protected]
To unsubscribe send an email to [email protected]
