tinc - May 2015 - IPv6 subnet routing

I've been trying out IPv6 networking with tinc and noticed that it will not
route smaller segments than /48
If I try to run ip -6 route add aaaa:bbbb:cccc:dddd::/64 dev tun0 I get
network unreachable
However if I run ip -6 route add aaaa:bbbb:cccc::/48 dev tun0 it works fine

Is this is a limitation in tinc or the kernel network stack itself?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20150521/1f4219b6/attachment.html>

On Thu, May 21, 2015 at 02:26:54PM +0000, Martin wrote:
> I've been trying out IPv6 networking with tinc and noticed that it will
not
> route smaller segments than /48
> If I try to run ip -6 route add aaaa:bbbb:cccc:dddd::/64 dev tun0 I get
> network unreachable
> However if I run ip -6 route add aaaa:bbbb:cccc::/48 dev tun0 it works fine
> 
> Is this is a limitation in tinc or the kernel network stack itself?
You should be able to add any route with any prefix just fine. But can
you show us the output of "ip -6 route show" and the exact command
that
you tried that fails?

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20150521/2f64f901/attachment.sig>

I have 2 nodes nodeA and nodeB
I'm using tinc 1.1pre11

-- nodeA(fd80:2015:2105:abcd::1) :

$ ip -6 route
fd80:2015:2105:abcd::1 dev tun0  proto kernel  metric 256
fd80:2015:2105:adcd::/64 dev tun0  metric 1024
fe80::/64 dev eth0  proto kernel  metric 256

$ ping6 fd80:2015:2105:abcd::1
PING fd80:2015:2105:abcd::1(fd80:2015:2105:abcd::1) 56 data bytes
64 bytes from fd80:2015:2105:abcd::1: icmp_seq=1 ttl=64 time=0.020 ms

$ ping6 fd80:2015:2105:abcd::2
connect: Network is unreachable

-- nodeB(fd80:2015:2105:abcd::2):

$ ip -6 route
fd80:2015:2105:abcd::2 dev tun0  proto kernel  metric 256
fd80:2015:2105:adcd::/64 dev tun0  metric 1024
fe80::/64 dev eth0  proto kernel  metric 25

$ ping6 fd80:2015:2105:abcd::2
PING fd80:2015:2105:abcd::2(fd80:2015:2105:abcd::2) 56 data bytes
64 bytes from fd80:2015:2105:abcd::2: icmp_seq=1 ttl=64 time=0.019 ms

$ ping6 fd80:2015:2105:abcd::1
connect: Network is unreachable


I can see in the debug output that the tinc daemons on each node is talking
to each other.
I suspect kernel having some internal settings as I don't see any debug
message when I do a ping6 to the other node.
If I change the ip -6 route on both nodes to /48 it works fine.

On Thu, 21 May 2015 at 16:19 Guus Sliepen <guus at tinc-vpn.org> wrote:
> On Thu, May 21, 2015 at 02:26:54PM +0000, Martin wrote:
>
> > I've been trying out IPv6 networking with tinc and noticed that it
will
> not
> > route smaller segments than /48
> > If I try to run ip -6 route add aaaa:bbbb:cccc:dddd::/64 dev tun0 I
get
> > network unreachable
> > However if I run ip -6 route add aaaa:bbbb:cccc::/48 dev tun0 it works
> fine
> >
> > Is this is a limitation in tinc or the kernel network stack itself?
>
> You should be able to add any route with any prefix just fine. But can
> you show us the output of "ip -6 route show" and the exact
command that
> you tried that fails?
>
> --
> Met vriendelijke groet / with kind regards,
>      Guus Sliepen <guus at tinc-vpn.org>
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20150521/e975b9a5/attachment.html>