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 communication inside the tun/tap device? Thanks,
Reinoud. On Thu, Oct 23, 2014 at 3:12 PM, Gert Doering <g...@greenie.muc.de> wrote: > 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 protocol (unlike UDP). > > So, OpenVPN in peer-to-peer mode will need --tcp-client on one side and > --tcp-server on the other (it doesn't matter which one is which, as > as soon as the TCP connection is up, it's "peer to peer" inside) > > gert > -- > USENET is *not* the non-clickable part of WWW! > // > www.muc.de/~gert/ > Gert Doering - Munich, Germany > g...@greenie.muc.de > fax: +49-89-35655025 > g...@net.informatik.tu-muenchen.de >
