Subject: Re: OpenVPN + tun(4) problem
To: Masao Uebayashi <uebayasi@brains.co.jp>
From: Bernd Ernesti <netbsd@lists.veego.de>
List: current-users
Date: 03/12/2006 11:30:33
On Sun, Mar 12, 2006 at 04:10:16PM +0900, Masao Uebayashi wrote:
> Hi!
>
> OpenVPN using tun(4) failed to me. Initialization sequence looked OK,
> but connection didn't work. (ping couldn't reach a tun peer.)
>
> If I cvs up src/sys/net/if_tun.{c,h} to -D 20050215, the problem was
> gone. Rui's IPv6 change is causing something maybe?
Hmm, see the mail on March 3rd on current-users from zul@netbsd-fr.org:
> Date: Fri, 3 Mar 2006 22:35:10 +0100
> From: zul@netbsd-fr.org
> Subject: RE : problem with sys/net/if_tun.c revision 1.80
> To: current-users@NetBSD.org
> Cc: Jukka Salmi <j+nbsd@2006.salmi.ch>
>
> in 1.80 we have change the tun behaviour to permit the use of ipv6 under
> tun. Now, the tun interface has more or less the same interface than
> OpenBSD's one. Try this patch on Makefile (vpnc Makefile in work).
>
> ifeq ($(shell uname -s), NetBSD)
> - CFLAGS += -DSOCKADDR_IN_SIN_LEN -DHAVE_SA_LEN
> + CFLAGS += -DSOCKADDR_IN_SIN_LEN -DHAVE_SA_LEN -DNEW_TUN
> SYSDEP=sysdep-bsd.o
Jukka confirmed that this solve the problem for him.
So, maybe we need to add something to openvpn too, whatever NEW_TUN in
vpnc does.
Bernd