<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 16/05/2014 15:31, Simon Deziel
wrote:<br>
</div>
<blockquote cite="mid:53762146.9020303@xelerance.com" type="cite">
<pre wrap="">
Hi Nick,
On 14-05-16 09:44 AM, Nick Howitt wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Having said that, If you put nothing in Openswan, it should follow
anything the Sonicwall requests.
</pre>
</blockquote>
<pre wrap="">
Even better! Thanks, I didn't know the OpenSwan's default proposal
intersected with the Sonicwall one.
</pre>
</blockquote>
I don't know if the Sonicwall overlaps with Openswan. My own
experience is with Drayteks, but I found that even setting Openswan
to 3DES, it would accept AES from the Draytek. I came to the
conclusion it was not worth setting anything in Openswan and then
control the cryptography from the Draytek end. It saved any possible
mismatch. I could not even get the strict flag to work - perhaps the
phase2alg bug.<br>
<br>
I do not have a huge experience, but all the devices I've used could
do 3DES as a minimum so a common denominator was always possible. In
reality I preferred AES128 over 3DES, and now I use AES256. I never
had to set anything in Openswan to achieve any of these.<br>
<br>
Nick<br>
<br>
<snip><br>
</body>
</html>