<div dir="ltr">It sounds like both clients are within the same IP range. You'll probably find that the first machine to connect is ok and the 2nd machine will not be able to connect simply because of the IP range.<div>
<br></div><div>If you look in /var/log/secure you should see something about the tunnel already being in use (I am paraphrasing) for the 2nd machines connection.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On 22 October 2013 05:18, klas <span dir="ltr"><<a href="mailto:openswan@k.flum.net" target="_blank">openswan@k.flum.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I've got two machines in the same LAN. Both have (as far as I can tell)<br>
identical configurations for ipsec and xl2tpd. Once machine can connect<br>
as client to the server, the other one can't.<br>
The clients and the server are both behind NAT.<br>
<br>
ipsec seems to come up fine for both machines, but machine 2 is not<br>
able to set up l2tp. It's sending one packet and gets no answer.<br>
<br>
Any pointers about how to troubleshoot this?<br>
<br>
Thanks<br>
Klas<br>
<br>
_______________________________________________<br>
<a href="mailto:Users@lists.openswan.org">Users@lists.openswan.org</a><br>
<a href="https://lists.openswan.org/mailman/listinfo/users" target="_blank">https://lists.openswan.org/mailman/listinfo/users</a><br>
Micropayments: <a href="https://flattr.com/thing/38387/IPsec-for-Linux-made-easy" target="_blank">https://flattr.com/thing/38387/IPsec-for-Linux-made-easy</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>
</blockquote></div><br></div>