2008/3/17, Jacco de Leeuw <<a href="mailto:jacco2@dds.nl" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">jacco2@dds.nl</a>>:<span class="q"><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Julien DELEAN wrote:<br> <br> > I've a problem with my roadwarriors. Some of them have the same ID_FQDN<br> > : '@example' and I can't change it.<br> <br> <br>This is the hostname configured on the client, so it is actually something<br>
that you can change.</blockquote></span><div><br>No I can't ask my customers to change their Windows hostname. <br>I
could try to dispatch my customers on different Openswan servers
depending their ID_FQDN in order to assure uniq ID_FQDN but it's really
really really hard for me to implement this in my production
environment.<br>
</div><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> > Does anybody know if non-unique ID for roadwarrior connections on an<br>
> Openswan Server is a really really bad thing ? Why ?<br>
<br> <br>AFAIK only Windows 2000/XP clients do this when NAT is involved.<br> I don't think it's in the official NAT-T RFC.</blockquote></span><div><br>All my roadwarriors are Windows 2000/XP/Vista clients.<br>Do you think that setting uniqids=no is an acceptable solution ?<br>
<br>Thanks<br><br></div>Julien DELEAN