<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">On Nov 29, 2020, at 18:33, Balaji Thoguluva <tbbalaji@gmail.com> wrote:<br><div dir="ltr"><blockquote type="cite"><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div>Thanks Paul. Do you have some reference/link to the known issue so I can get more information? </div></div></div></blockquote><div><br></div><div>Look for “revive” in the CHANGES file or git log messages.</div><div><br></div><br><blockquote type="cite"><div dir="ltr"><br><div class="gmail_quote"><div class="gmail_attr" dir="ltr">On Sun, Nov 29, 2020 at 6:00 PM Paul Wouters <<a href="mailto:paul@nohats.ca">paul@nohats.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">On Nov 29, 2020, at 17:07, Balaji Thoguluva <<a href="mailto:tbbalaji@gmail.com" target="_blank">tbbalaji@gmail.com</a>> wrote:<br>
> <br>
> <br>
> Hi Folks,<br>
> <br>
> I am using Linux Libreswan 3.25 (netkey) on 4.14.35.<br>
> <br>
> 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.<br>
> <br>
> 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.<br>
<br>
That is a known bug. I believe it was fixed in 3.27.<br>
<br>
Paul<br>
</blockquote></div>
</div></blockquote></body></html>