On Sunday June 5, j...@yonan.net wrote:
>
> I don't think it's possible for the current TAP-Win32 driver to do OSI
> Layer 3 with a network/netmask setting. This gets back to the same reason
> why --ifconfig-pool-linear doesn't work on Windows: The TAP-Win32 driver
> is a TAP driver from the
On Saturday June 4, j...@yonan.net wrote:
>
> On Sat, 4 Jun 2005, Neil Brown wrote:
> > A "real" tun driver (by which I assume you mean one that support
> > point-to-point addressing) isn't needed to avoid "losing" 2 addresses
> > per client.
>
On Saturday June 4, ov_de...@l3h.de wrote:
>
> I think, a real tun driver for Windows is a killer feature. This would make
> large heterogenous VPN setups much easier, because you could provide your
> clients a layer-3 VPN without "losing" 2 addresses per client.
>
A "real" tun driver (by whic
I have a small number of wishlist items.
I feel the first two are 2.0.x items, but maybe they should be 2.1 items.
I'll add them to the wiki under 2.0 unless someone suggests otherwise.
1/ When using --daemon and --management-hold, openvpn should
daemonize before entering the 'hold' state.
I
On Tuesday July 27, j...@yonan.net wrote:
> Neil,
>
> Comments Inline below...
>
> Neil Brown said:
>
> >
> >
> > As was hinted at with the previous patch, this patch introduces a new
> > config option "net-type". It can be either "
On Tuesday July 27, j...@yonan.net wrote:
> I agree with you that tunnel device type and subnet vs. point-to-point mode
> are mutually exclusive properties.
>
> My main concern is preventing an explosion in the size of the parameter
> permutation space, where the code has to handle 4 cases of dev/
On Tuesday July 27, j...@yonan.net wrote:
> PUSH_DEFINED is currently unused, so overall I don't have any problem with
> this. Probably when something gets written that needs PUSH_DEFINED, the
> subtletes of how it should operate will become more apparent.
>
It was used in beta6 which is what I
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
My server that I hope to use as an OPENVPN server is multi-homed.
i.e. it has multiple network interfaces and multiple addresses on
multiple subnets.
When my openvpn client (on my notebook) tries to talk to it, it
sometimes gets a reply from a different IP address than it sent the
request to, and
12 matches
Mail list logo
