The problem is that the nl package was built with 2.1 version, and I have used this.
On a different topic: I found an issue, you probably want to fix that: In reliable_pid_in_range1() function, the third parameter(extent) is an unsigned int. However, this function is being called by reliable_pid_min(), passing 0x80000000u as the value to extent. On a 16 bit machine (int is 16 bit) this will never work. The type of extent need to change to unsigned long and not int. Tiran -----Original Message----- From: Adriaan de Jong [mailto:dej...@fox-it.com] Sent: Tuesday, December 13, 2011 11:31 AM To: Gert Doering; Tiran Kaskas Cc: openvpn-devel@lists.sourceforge.net Subject: RE: [Openvpn-devel] Problem with alloc_buf_gc function > -----Original Message----- > From: Gert Doering [mailto:g...@greenie.muc.de] > > On Mon, Dec 12, 2011 at 09:32:51AM +0000, Tiran Kaskas wrote: > > Is there a problem connecting a client running 2.1.4 (the one with > polarssl) to a server running 2.0.9? > > Well, the default crypto algorithms are not compatible between polarssl > and openssl-using openvpn. So you'd need to change the crypto settings > on the openssl-openvpn [--cipher] - and upgrade to 2.2, while at it. To be a little more specific: PolarSSL doesn't support blowfish (BF-CBC), a good option would be AES (AES-xxx-CBC). You can see the supported ciphers using --list-ciphers. Adriaan
