Ok, Thanks.
I understood the term mode wrong.
So the main mode can be p2p or server to denote the openvpn protocol inside
tcp or udp(stateless) session. Initially I thought the term mode is used to
denote server, client or udp.
Hi,
On Thu, Oct 23, 2014 at 03:42:54PM -0600, Reinoud Koornstra wrote:
> 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?
Please READ what I write, so I don't have to repeat it.
TCP imposes an imbalance between the peers (one has to be the listening
and one has to be the connecting instance), but the OpenVPN protocol
*inside*
the TCP session will still be "point to point mode (p2p)"
> 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,
tun/tap is just a network interface, so do with it what you want - setup
ip addresses and routing, set up firewalling, set up policy routing, etc. -
OpenVPN won't care, and just transport packets entering the tun/tap
interface to the other side, and deliver to the remote tun/tap interface.
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
