Hi Gert,

IPv6 works just fine with my setup, at least in my "simple" setup:

I have a VirtualBox VM with OpenWRT running on my internet server, that
gets a (6to4) IPv6 address from HEnet (sadly my server provider doesn't
yet seem to know anything about IPv6) including a /48 subnet and runs an
OpenVPN server (2.3-alpha3) which distributes (local)IPv4 and
(global)IPv6 addresses to the clients.
Now I have several OpenVPN routers (i.e. my home internet router) that
connect to the OpenVPN server, get a global IPv6 address (with a /56
subnet) from the server and distribute global IPv6 addresses from the
/56 subnet to the LAN-clients via dnsmasq6.

All of this works like a charm, so I'd say there's no problem with
routing IPv6.
But I'd be grateful to have someone with more experience look at it and
test it with more complex scenarios, since I've just started with IPv6
recently. I'm willing to make it perfect, so I'm eager to learn.

Joachim

Am 04.10.2012 12:50, schrieb Gert Doering:
> Hi,
> 
> On Thu, Oct 04, 2012 at 11:29:49AM +0200, Joachim Schlipper wrote:
>> as I didn't get reply in the forum (well, except for that spambot who
>> kindly wrote on the thread), I dare to post my question again here.
>>
>> I'm quite eager to contribute my work on the OpenVPN netifd integration
>> into the repository, but don't know which way to go.
> 
> I'm neutral on whether netifd is "right" or "wrong", but want to comment
> on something else.
> 
> In the forum post, I've seen that you call openvpn with --route-noexec,
> and leave routing entries to netifd.  I'm fine with that, but please make
> sure this also works for IPv6.
> 
> IPv6 support in OpenVPN has come a long way, and it would be a shame
> to see a new framework support only the IPv4 side of things.
> 
> (openvpn-devel-* are the packages that have full IPv6 support, based
> on upstream git of the soon-to-be released 2.3 version)
> 
> If you need a remote server that has working IPv6 and will push
> IPv6 routes, to see that everything works, let me know and I'll set up 
> something.
> 
> 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