Hi Paul, Can I backport the fixes shown below to the 3.25 version?
If yes, can you please provide me the steps on how to do it as I am not much familiar with it? * pluto: Revive (with back-off) auto=start conns that receive Delete/Notify [Paul] * pluto: Revive auto=start conns that receive Delete/Notify [Paul/Hugh/Andrew] Thanks, Balaji On Sun, Nov 29, 2020 at 7:50 PM Paul Wouters <[email protected]> wrote: > On Nov 29, 2020, at 18:33, Balaji Thoguluva <[email protected]> wrote: > > > > Thanks Paul. Do you have some reference/link to the known issue so I can > get more information? > > > Look for “revive” in the CHANGES file or git log messages. > > > > On Sun, Nov 29, 2020 at 6:00 PM Paul Wouters <[email protected]> wrote: > >> On Nov 29, 2020, at 17:07, Balaji Thoguluva <[email protected]> wrote: >> > >> > >> > Hi Folks, >> > >> > I am using Linux Libreswan 3.25 (netkey) on 4.14.35. >> > >> > The very first time, IKEv2/IPsec tunnel gets established correctly. I >> establish the tunnel by triggering a RADIUS packet matching the above >> parameters and this packet triggers the tunnel from Libreswan to the other >> end. >> > >> > Now I tear down the tunnel from the other end and I verified there is >> no tunnel/SA's in Libreswan. Now if I again attempt to establish the same >> tunnel by triggering the RADIUS packet, then the tunnel attempt from >> Libreswan fails. >> >> That is a known bug. I believe it was fixed in 3.27. >> >> Paul >> >
_______________________________________________ Swan-dev mailing list [email protected] https://lists.libreswan.org/mailman/listinfo/swan-dev
