Ok, clear, to TCP cannot be used in point to point mode (p2p) then, because
in case of tcp we must have a client and a server?
Inside the tun or tap interface, can we specify the protocol and port
number used for any communications inside the tun/tcp interface or do we
allow any protocol/port for c
Hi,
On Thu, Oct 23, 2014 at 02:04:10PM -0600, Reinoud Koornstra wrote:
> In my understanding, there is no client or server in p2p mode.
True, as far as the OpenVPN protocol is concerned.
False, as far as TCP is concerned, because you MUST have a client and a
server in TCP - it's not a symmetric
In my understanding, there is no client or server in p2p mode. In this case
you're trying to establish a secure connection between two gateways using
openvpn like a tunnel. Is my understanding wrong about this? Besides this,
I still stumble upon the issue of specifying just tcp in the remote
sectio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Here's the summary of the previous IRC meeting.
- ---
COMMUNITY MEETING
Place: #openvpn-devel on irc.freenode.net
List-Post: openvpn-devel@lists.sourceforge.net
Date: Thursday 23rd Oct 2014
Time: 18:00 UTC
Planned meeting topics for this meet
Hi,
On Thu, Oct 23, 2014 at 01:24:45PM -0600, Reinoud Koornstra wrote:
> The idea in my case is to have a point-to-point connection where both hosts
> listen on port 443 tcp instead of port 1194 udp to setup the point-to-point
> connection.
If both listen, who calls out? In TCP mode, you need to
Hello Everyone,
I read the manpage here: doc/openvpn.8
remote 198.19.34.56 443 tcp
However, when you configure this in your configuration file, you cannot do
this:
in src/openvpn/options.c:
/*
* If "proto tcp" is specified, make sure we know whether it is
* tcp-client or tcp-server.
Hi Steffan,
Patch attached.
-Lev
2014-10-23 10:52 GMT+03:00 Steffan Karger :
> Hi Lev,
>
> On 10/21/2014 09:33 AM, Lev Stipakov wrote:
>>
>> Thanks for your comments. I have fixed (1) and (2) - well, reusing
>> existing code in (2) has fixed also (1).
>
> Thanks! Do you have the patch somewhere
Hi Lev,
On 10/21/2014 09:33 AM, Lev Stipakov wrote:
>
> Thanks for your comments. I have fixed (1) and (2) - well, reusing
> existing code in (2) has fixed also (1).
Thanks! Do you have the patch somewhere for us to look at?
> Regarding (3) - I don't have much experience in crypto thing, so it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Please surf to http://sourceforge.net/p/openvpn/mailman/openvpn-announce/ and
> read the
post titled "[Openvpn-announce] New OpenVPN Windows installers (I004 and
I604) released" by Samuli.
>
> You'll see that OpenVPN needs to apply the latest secu
Hi,
On Thu, Oct 23, 2014 at 07:30:48AM +0200, Lisa Minogue wrote:
> I'm no expert of OpenVPN or OpenSSL and it be nice of you if you could tell
> me whether the latest OpenVPN's installers for Microsoft Windows OS have been
> built with "no-ssl3" flag in OpenSSL 1.0.1j.
No, they haven't.
Becau
Hi Samuli
I'm no expert of OpenVPN or OpenSSL and it be nice of you if you could tell me
whether the latest OpenVPN's installers for Microsoft Windows OS have been
built with "no-ssl3" flag in OpenSSL 1.0.1j.
Regards.
Lisa
-
Mail.be, WebMail
Please surf to http://sourceforge.net/p/openvpn/mailman/openvpn-announce/ and
read the post titled "[Openvpn-announce] New OpenVPN Windows installers (I004
and I604) released" by Samuli.
You'll see that OpenVPN needs to apply the latest security fixes from OpenSSL.
Lisa
> -
Please surf to http://sourceforge.net/p/openvpn/mailman/openvpn-announce/ and
read the post titled "[Openvpn-announce] New OpenVPN Windows installers (I004
and I604) released" by Samuli.
The answer you're looking for is there.
Lisa
>
> From: Илья Шипици
13 matches
Mail list logo
