On 12/29/2011 01:29:00 PM, Gert Doering wrote:
> Now I wouldn't know how to enable ip forwarding on Windows, and I
> wouldn't
> even think of running an OpenVPN server on Windows, but supposedly it
> can
> be done. Let someone else chime in and answer that...
Perhaps on the openvpn-users list in
Hi,
On Thu, Dec 29, 2011 at 07:21:41PM +, Tiran Kaskas wrote:
> Well, the vpn server runs on windows.
Why would you want to do that? But even though - you need to enable
routing on the box, if you want it to be a router.
> You mean that every packet received from the outside should be forwa
TouchDown (www.nitrodesk.com)
-Original Message-
From: Karl O. Pinc [k...@meme.com]
Received: יום חמישי, 29 דצמ 2011, 18:38
To: Tiran Kaskas [tiran.kas...@telit.com]
CC: openvpn-devel@lists.sourceforge.net [openvpn-devel@lists.sourceforge.net]
Subject: Re: [Openvpn-devel] Problem with
On 12/29/2011 08:24:54 AM, Gert Doering wrote:
> Linux needs to know that it is to be a router:
>
> # echo 1 >/proc/sys/net/ipv4/ip_forward
See /etc/sysctl.conf (man sysctl.conf) to set
forwarding at boot.
Karl
Free Software: "You don't pay back, you pay forward."
-- Robert
Hi,
On Thu, Dec 22, 2011 at 10:07:42AM +, Tiran Kaskas wrote:
> It seems like I am through with the vpn initialization, and seems like the
> session is created successfully.
> Now, I start sending data to some server from the client side (I have an
> application which opens a socket to googl
nvpn-devel@lists.sourceforge.net
Subject: Re: [Openvpn-devel] Problem with alloc_buf_gc function
Indeed, a large model is used
-Original Message-
From: Gisle Vanem [mailto:gva...@broadpark.no]
Sent: Wednesday, December 14, 2011 11:45 AM
To: openvpn-devel@lists.sourceforge.net
Subject: Re: [Ope
Indeed, a large model is used
-Original Message-
From: Gisle Vanem [mailto:gva...@broadpark.no]
Sent: Wednesday, December 14, 2011 11:45 AM
To: openvpn-devel@lists.sourceforge.net
Subject: Re: [Openvpn-devel] Problem with alloc_buf_gc function
"Tiran Kaskas" wrote:
> Alr
"Tiran Kaskas" wrote:
Already done the ssl part, only polarssl. It is working perfect and does
support 16bit with no change.
You got all the data in PolarSSL, LZO and OpenVPN to fit in a 16-bit
data-segment of 64 kByte? I'll be amazed. What memory model would
be needed to link in all the cod
ering; openvpn-devel@lists.sourceforge.net
> Subject: RE: [Openvpn-devel] Problem with alloc_buf_gc function
>
> Thanks.
> Already done the ssl part, only polarssl. It is working perfect and
> does support 16bit with no change.
>
> -Original Message-
> From: David Sommerseth [
; openvpn-devel@lists.sourceforge.net
Subject: Re: [Openvpn-devel] Problem with alloc_buf_gc function
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/12/11 21:22, Tiran Kaskas wrote:
> The problem is that the nl package was built with 2.1 version, and I
> have used this.
>
> On
...@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.
.
-Original Message-
From: Gert Doering [mailto:g...@greenie.muc.de]
Sent: Tuesday, December 13, 2011 11:19 PM
To: Tiran Kaskas
Cc: Adriaan de Jong; Gert Doering; openvpn-devel@lists.sourceforge.net
Subject: Re: [Openvpn-devel] Problem with alloc_buf_gc function
Hi
On Tue, Dec 13, 2011 at 08:22:36PM
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 reliable_pid
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 +, Tiran Kaskas wrote:
&g
> -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 ar
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 chang
e/downloads.html>
kind regards,
David Sommerseth
(PS! Also, please don't top-post)
> -Original Message- From: Tiran Kaskas
> [mailto:tiran.kas...@telit.com] Sent: Monday, December 12, 2011 9:42
> AM To: Fabian Knittel Cc: openvpn-devel@lists.sourceforge.net Subject:
>
hanks
-Original Message-
From: Tiran Kaskas [mailto:tiran.kas...@telit.com]
Sent: Monday, December 12, 2011 9:42 AM
To: Fabian Knittel
Cc: openvpn-devel@lists.sourceforge.net
Subject: Re: [Openvpn-devel] Problem with alloc_buf_gc function
You are right, I somehow mixed the data ptr wit
...@avona.com]
Sent: Monday, December 12, 2011 12:11 AM
To: Tiran Kaskas
Cc: openvpn-devel@lists.sourceforge.net
Subject: Re: [Openvpn-devel] Problem with alloc_buf_gc function
Hi Tiran,
Am 11.12.2011 21:57, schrieb Tiran Kaskas:
> Looking into the function alloc_buf_gc() in file buffer.c, it retu
Hi Tiran,
Am 11.12.2011 21:57, schrieb Tiran Kaskas:
> Looking into the function alloc_buf_gc() in file buffer.c, it returns a
> struct buffer, which seems to me is allocated on the stack, which is
> causing an issue, I believe, since the function calling alloc_buf_gc()
> will work on a buffer whi
Looking into the function alloc_buf_gc() in file buffer.c, it returns a struct
buffer, which seems to me is allocated on the stack, which is causing an issue,
I believe, since the function calling alloc_buf_gc() will work on a buffer
which becomes garbage.
Please confirm I am not missing someth
21 matches
Mail list logo
