IPv6, ULAs and FreeBSD

[Guus Sliepen]

On Tue, May 24, 2016 at 08:17:07AM +0200, Niklaas Baudet von Gersdorff wrote:

> I want to serve IPv4 subnets 10.1.0.0/16 (machine A) and 10.2.0.0/16
> (machine B), and IPv6 subnets fd16:dcc0:f4cc:0:0:1::/96 (machine A) and
> fd16:dcc0:f4cc:0:0:2::/96 (machine B) respectively. The jails are
> connected on lo1.
[...]
>     A $ cat /usr/local/etc/tinc/klaas/tinc-up
>     ifconfig $INTERFACE inet6 fd16:dcc0:f4cc:0:0:1:0:1 prefixlen 80
>     route -6 add -host fd16:dcc0:f4cc:0:0:2:0:1 fd16:dcc0:f4cc:0:0:1:0:1
>     route -6 add -net  fd16:dcc0:f4cc:0:0:2::/96  fd16:dcc0:f4cc:0:0:1:0:1
>     #route -6 add -ifp $INTERFACE -host fd16:dcc0:f4cc::2:0:1    fd16:dcc0:f4cc::1:0:1
>     #route -6 add -ifp $INTERFACE -net  fd16:dcc0:f4cc::2:0:0/96 fd16:dcc0:f4cc::1:0:1

All those route commands are unnecessary. The ifconfig command already
ensures there is a route for fd16:dcc0:f4cc::/80 to tinc's interface.

> This is tinc.conf on machine A:
> 
>     Name = A
>     ConnectTo = B
>     BindToAddress = <public-ipv4>
>     BindToAddress = <public-ipv6>
>     Device = /dev/tap0

Hm, what if you use Device = /dev/tun0 instead?

If this still doesn't work, then try to find out what happens with the
packets you are sending. Run tinc in the foreground (use the options -d5 -D),
and then run ping6 fd16:dcc0:f4cc:0:0:2:0:1 in another terminal. Does
tinc see the packets? Does it send them to B? If so, the problem might
be on B. If it doesn't get the packets, try tcpdump on all the
interfaces to see where those packets are going.

-- 
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/20160524/bf42391c/attachment.sig>