Hi
On Tue, Dec 13, 2011 at 08:22:36PM +, Tiran Kaskas wrote:
> The problem is that the nl package was built with 2.1 version, and I have
> used this.
2.1+nl patches is fine. 2.0 is not what you want.
> On a different topic: I found an issue, you probably want to fix that:
> In
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/12/11 18:14, David Sommerseth wrote:
> When using OpenVPN 2.2 on clients and server with Windows based
> clients, it will try to push IPv6 packets through the tunnel. This
> causes the server log to be filled up with log entries like this:
>
Hi,
On Tue, Dec 13, 2011 at 06:14:00PM +0100, David Sommerseth wrote:
> When using OpenVPN 2.2 on clients and server with Windows based
> clients, it will try to push IPv6 packets through the tunnel. This
> causes the server log to be filled up with log entries like this:
>
> Wed Jun 29
When using OpenVPN 2.2 on clients and server with Windows based
clients, it will try to push IPv6 packets through the tunnel. This
causes the server log to be filled up with log entries like this:
Wed Jun 29 22:12:51 2011 username/1.2.3.4:56990 Need IPv6 code in
mroute_extract_addr_from_packet
> -Original Message-
> From: Gert Doering [mailto:g...@greenie.muc.de]
>
> On Mon, Dec 12, 2011 at 09:32:51AM +, 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
Hi,
On Mon, Dec 12, 2011 at 09:32:51AM +, 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
