Ok, after some heavy testing this won't fix the problem.

Besides NetBSD wants an 'activate' after the lladdr, NetBSD won't
calculate the inet6 address using the set lladdr, because somehow the
ifconfig command will be provided _before_ the lladdr is set. Even the
generic openvpn based lladdr is set _before_ the custom lladdr is set.

Dunno why, but it has to be fixed anyway. I'll look deeper into that in
my free time soon.

regards,
Frederic Jaeckel

On Tue, 22 Dec 2009 12:15:45 +0100
Frederic Jaeckel <jch...@jc-ix.net> wrote:

> Hi,
> 
> todays openvpn isn't supporting NetBSDs way to set the lladdr for
> tap(4) devices.
> 
> Here's the patch to support this.
> 
> Please integrate this in the next release.
> 
> best regards and thanks for the work,
> Frederic Jaeckel
> 
> --- lladdr.c    2009-12-22 12:08:23.000000000 +0100
> +++ lladdr.c.b  2009-12-22 12:08:14.000000000 +0100
> @@ -36,6 +36,11 @@  
>                     "%s %s lladdr %s",
>                     IFCONFIG_PATH,
>                     ifname, lladdr);
> +#elif defined(TARGET_NETBSD)
> +  argv_printf (&argv,
> +                   "%s %s link %s",
> +                   IFCONFIG_PATH,
> +                   ifname, lladdr);
>  #elif defined(TARGET_DARWIN)
>    argv_printf (&argv,
>                     "%s %s lladdr %s",

Attachment: signature.asc
Description: PGP signature

Reply via email to