Делаем
ip tuntap add tap0 mode tap user root
ip link set tap0 up
ip link add br0 type bridge
ip link set tap0 master br0
ip link set dev eth0 down
ip addr flush dev eth0
ip link set dev eth0 up
ip link set eth0 master br0
ip link set dev br0 up
получаем мост br0 и сетевые интерфейсы eth0,tap0
Пробуем поднять ipv4 адрес , тут всё ок
$ ip a add 10.0.0.4/8 dev tap0
$ ping -c1 10.0.0.4
PING 10.0.0.4 (10.0.0.4) 56(84) bytes of data.
64 bytes from 10.0.0.4: icmp_seq=1 ttl=64 time=0.011 ms
--- 10.0.0.4 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.011/0.011/0.011/0.000 ms
Пробую поднять ipv6
$ ip -6 address add dev tap0 scope link fe80::21b:21ff:febb:5db0/64
$ ip -6 address add dev tap0 scope global fddd:abcd:1234:5::4/64
$ ip a s tap0
3: tap0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast master br0 state DOWN group default qlen 500
link/ether c2:53:a9:ca:7c:3c brd ff:ff:ff:ff:ff:ff
inet 10.0.0.4/8 scope global tap0
valid_lft forever preferred_lft forever
inet6 fddd:abcd:1234:5::4/64 scope global tentative
valid_lft forever preferred_lft forever
inet6 fe80::21b:21ff:febb:5db0/64 scope link tentative
valid_lft forever preferred_lft forever
#Проверяем
$ ping6 -c1 -W5 fddd:abcd:1234:5::4
PING fddd:abcd:1234:5::4(fddd:abcd:1234:5::4) 56 data bytes
--- fddd:abcd:1234:5::4 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
$ ping6 fddd:abcd:1234:5::4%tap0
unknown host
$ ip -6 r
fddd:abcd:1234:5::/64 dev tap0 proto kernel metric 256
fe80::/64 dev eth0 proto kernel metric 256
fe80::/64 dev br0 proto kernel metric 256
fe80::/64 dev tap0 proto kernel metric 256
Ну оно и понятно - tentative
В чем причина, что на tap-устройстве не могу поднять ipv6 или что я упустил ?
