Hi,

this little patch does the trick. Busybox ifconfig just just doesn't
want the 'inet6' parameter, the rest is the same.

Joachim

diff -Naur old/src/openvpn/tun.c new/src/openvpn/tun.c
--- old/src/openvpn/tun.c       2012-09-11 11:02:41.000000000 +0200
+++ new/src/openvpn/tun.c       2012-09-11 12:27:30.304436864 +0200
@@ -760,7 +760,7 @@
       if ( do_ipv6 )
        {
          argv_printf (&argv,
-                         "%s %s inet6 add %s/%d",
+                         "%s %s add %s/%d",
                          IFCONFIG_PATH,
                          actual,
                          ifconfig_ipv6_local,


Am 11.09.2012 10:45, schrieb Gert Doering:
> Hi,
> 
> On Tue, Sep 11, 2012 at 04:12:14PM +0800, Mirko Vogt wrote:
> [..]
>>> and while I see
>>> some space benefit in not depending on the "ip" package, I wonder whether
>>> this could be changed to "have *ENABLE_IPROUTE2 default to 'on'", so the
>>> pre-built packages *work*, and if someone is really space constrained,
>>> he can turn it off...?
>>>
>>> That is, apply the following patch... 
>>
>> The disadvantage in regard of space is enormous.. if there's no other
>> way to get this fixed, okay, I'm fine with that.
> 
> Defaulting to ENABLE_IPROUTE2 would be a quick fix (and compared to
> the openssl dependency, "ip" is tiny :-) - I hope polarssl gets blowfish
> support "RSN", so the default).
> 
>> However busybox's ifconfig IS capable of manage ipv6 settings, so I'd
>> rather like to see openvpn interacting with ifconfig correctly.
> 
> I'll try to figure out how busybox's ifconfig wants to be called, and
> prepare a patch for OpenVPN to handle that.
> 
> This would have to be a local patch in the package feed, as upstream
> is unlikely to accept a special #ifdef for LINUX_BUSYBOX_IFCONFIG.
> 
> gert
> 
> 
> 
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> 
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to