I did set one.
On the gateway:
$ ip addr show dev tun0
3: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UNKNOWN group default qlen 100
link/none
inet 172.29.0.1 peer 172.29.0.2/32 scope global tun0
valid_lft forever preferred_lft forever
inet6 fd97:594e:1bc4:0:c82a:3298:fec4:4eb9/128 scope global
valid_lft forever preferred_lft forever
inet6 fe80::2018:18bb:f08:2acf/128 scope link
valid_lft forever preferred_lft forever
And on the mesh node:
$ ip addr show dev tun0
5: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UNKNOWN group default qlen 100
link/none
inet 172.29.0.6 peer 172.29.0.5/32 scope global tun0
valid_lft forever preferred_lft forever
inet6 fe80::6510:6a4d:f1d5:ffad/64 scope link flags 800
valid_lft forever preferred_lft forever
Looks like they exist and are different.
On Tue, Jun 18, 2019 at 7:54 PM Juliusz Chroboczek <[email protected]> wrote:
>
> Is there an IPv6 link-local address on the tun0 interface? Please show us
> the output of
>
> ip addr show dev tun0
>
> If there's no link-local address (Linux kernel bug), then you should add
> one manually:
>
> ip addr add fe80::1/64 dev tun0
>
> You should use different link-locals on the two sides of the tunnel
> (e.g. fe80::1 on one side and fe80::2 on the other).
>
> -- Juliusz
_______________________________________________
Babel-users mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/babel-users
