Am Di, den 27.07.2004 schrieb Neil Brown um 4:29:
> I want to use tun devices (as I am only interested in IP traffic, and
> I want some checking of source IP address to be done) but I want to
> treat the collection of openvpn instances (the server and several
> clients) as a single subnet.
> A par
As was hinted at with the previous patch, this patch introduces a new
config option "net-type". It can be either "ptp" or "subnet".
If net-type is not explicitly given then:
if "dev" is "tun", "net-type" will be "ptp"
if "dev" is "tap", "net-type" will be "subnet"
If it is given, then it ov
This is the third for 4 patches. Possible it is a little more
controversial.
This patch doesn't actually make any functional change to openvpn.
However it prepares the way for a functional change to be implemented
in the next patch.
(Ignoring null,) openvpn has two types for devices, tun and tap
This patch is of little import, but I thought I would submit it
anyway.
openvpn has a "PUSH_DEFINED" macro which is used to determine how the
configuration summary, which is exchanged for consistency checking, is
created.
PUSH_DEFINE should be equivalent to "something might get pushed". It
is cu
Hi.
This is the first of 4 patches that I would like to offer for
openvpn.
They are against 2.0_beta7.
This first one is a refinement of a patch I posted earlier which, at
that time, didn't work.
The purpose of the patch is to use the IP_PKTINFO socket option to get
and set the local address fo
