Ok, je suis.
Avant d'aller plus loin, j'ai rebooté l'ipfire me disant que les éléments de préparation à l'ipv6 pouvait déjà avoir un impact. Bingo
[root@ipfire37700 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc fq_codel state DOWN group default qlen 1000
link/tunnel6 :: brd ::
3: sit0@NONE: <NOARP> mtu 1480 qdisc fq_codel state DOWN group default qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0
4: red0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 50:3e:aa:0e:ee:51 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.10/24 brd 192.168.1.255 scope global noprefixroute red0
valid_lft forever preferred_lft forever
inet6 2a0c:8c80:11:c010:523e:aaff:fe0e:ee51/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 150846sec preferred_lft 64446sec
inet6 fe80::523e:aaff:fe0e:ee51/64 scope link
valid_lft forever preferred_lft forever
5: green0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:21:85:5f:13:d9 brd ff:ff:ff:ff:ff:ff
inet 192.168.24.1/24 brd 192.168.24.255 scope global green0
valid_lft forever preferred_lft forever
inet6 fe80::221:85ff:fe5f:13d9/64 scope link
valid_lft forever preferred_lft forever
Du coup, pour mon IPV6_IP je peux mettre celle prise par la pate RED : 2a0c:8c80:11:c010:523e:aaff:fe0e:ee51/64
?