Hi,<br>
<br>
Speaking about bug 1004, is there any solution to this issue? An rc version with a fix, a workaround or something?<br>
<br>BR,<br>Peter<br><br><div class="gmail_quote">On Fri, Mar 20, 2009 at 10:48 PM, Paul Wouters <span dir="ltr"><<a href="mailto:paul@xelerance.com">paul@xelerance.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Fri, 20 Mar 2009, Christian Huldt wrote:<br>
<br>
> Date: Fri, 20 Mar 2009 12:02:36 +0100<br>
> From: Christian Huldt <<a href="mailto:christian@solvare.se">christian@solvare.se</a>><br>
> To: <a href="mailto:users@openswan.org">users@openswan.org</a><br>
> Subject: [Openswan Users] l2tp traffic outside ipsec after upgrading to 2.6.20<br>
<div class="im">><br>
> I updated openswan from 2.4.13 to 2.6.20 as there is a need to deal with<br>
> a few users behind the same remote NAT.<br>
> (Would that require that I switch to klips?)<br>
><br>
> now with basically the same config as before (I added OE=off and<br>
> protostack=netkey) it seems as the l2tp response (xl2tpd-1.1.11) is<br>
> going outside the ipsec tunnel...<br>
><br>
> I don't quite understand this...<br>
<br>
</div><a href="http://bugs.xelerance.com/view.php?id=1004" target="_blank">http://bugs.xelerance.com/view.php?id=1004</a><br>
<font color="#888888"><br>
Paul<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
<a href="mailto:Users@openswan.org">Users@openswan.org</a><br>
<a href="http://lists.openswan.org/mailman/listinfo/users" target="_blank">http://lists.openswan.org/mailman/listinfo/users</a><br>
Building and Integrating Virtual Private Networks with Openswan:<br>
<a href="http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155" target="_blank">http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155</a><br>
</div></div></blockquote></div><br>