Alberto,
Here is a patch against 1.4.0 that tries the 2.4 TUN/TAP interface then
falls back to 2.2 if it fails. I don't have access to a 2.2 machine so I
have not been able to test. Let me know if it works.
James
On Thu, 8 May 2003, Alberto Gonzalez Iniesta wrote:
> On Thu, May 08, 2003 at
Matthias Andree said:
> On Thu, 08 May 2003, James Yonan wrote:
>
> > OpenVPN's config script assumes that if 2.4 headers are present (i.e.
> > if_tun.h), then it should build for the 2.4 tun/tap driver.
>
> This may not be true for build hosts of a distributor, who needs the
> most conservativ
On Thu, 08 May 2003, James Yonan wrote:
> OpenVPN's config script assumes that if 2.4 headers are present (i.e.
> if_tun.h), then it should build for the 2.4 tun/tap driver.
This may not be true for build hosts of a distributor, who needs the
most conservative code if he's still shipping 2.2 kern
On Thu, 08 May 2003, James Yonan wrote:
> Release Notes:
>
> This release adds options for persistence of replay protection information
> across sessions, pass through of IPv4 TOS bits from the TUN/TAP device to the
> UDP link, some advanced MTU control options, moderate revamping of the build
>
On Thu, May 08, 2003 at 08:30:34AM -, James Yonan wrote:
> Alberto Gonzalez Iniesta said:
>
> > When compiled with 2.4.* kernel headers (libc6-dev 2.2.5-14.3 headers)
> > it detects this header file and defines HAVE_LINUX_IF_TUN_H. This allow
> > openvpn to work correctly with 2.4.18 kernels
Alberto Gonzalez Iniesta said:
> Hi all,
>
> Sorry for the delay forwarding this email, but I don't find time to
> breath lately (and thus Oxygen does not make it to my brain :)
>
> Hope it's an easy one.
>
>
> - Forwarded message from Robert de Bath -
>
> From: Robert de Bath
>
