I see a similar content of /root/anaconda-ks.cfg
If I recall correctly, I havenât seen any option to activate or deactivate ip6. It is just enabled by default. IMO something that can potentially give an extra way in for the badguysâŠ
Anaconda is sometimes difficult to understand, but I donât think this is a bug. Next time you install with interactive, review the network settings before pressing âDoneâ
[root@leo lsd]# ping6 -c2 ff02::1%eno1
PING ff02::1%eno1(ff02::1%eno1) 56 data bytes
64 bytes from fe80::96de:80ff:febf:d656%eno1: icmp_seq=1 ttl=64 time=0.242 ms
64 bytes from fe80::1e6f:65ff:febe:f1ae%eno1: icmp_seq=1 ttl=64 time=0.271 ms (DUP!)
64 bytes from fe80::28c4:dfff:feca:6af3%eno1: icmp_seq=1 ttl=64 time=0.343 ms (DUP!)
64 bytes from fe80::3436:63ff:fe64:3161%eno1: icmp_seq=1 ttl=64 time=0.361 ms (DUP!)
64 bytes from fe80::3061:65ff:fe37:6136%eno1: icmp_seq=1 ttl=64 time=0.369 ms (DUP!)
64 bytes from fe80::3032:65ff:fe65:3032%eno1: icmp_seq=1 ttl=64 time=0.424 ms (DUP!)
64 bytes from fe80::3837:65ff:fe37:3963%eno1: icmp_seq=1 ttl=64 time=0.452 ms (DUP!) 64 bytes from fe80::fa1a:67ff:fe51:677c%eno1: icmp_seq=1 ttl=64 time=0.458 ms (DUP!)
64 bytes from fe80::3090:1bff:feaf:fe0a%eno1: icmp_seq=1 ttl=64 time=0.465 ms (DUP!)
64 bytes from fe80::a889:6dff:fe61:b633%eno1: icmp_seq=1 ttl=64 time=0.512 ms (DUP!)
64 bytes from fe80::4a51:b7ff:fe99:93fa%eno1: icmp_seq=1 ttl=64 time=48.7 ms (DUP!)
64 bytes from fe80::ee88:92ff:febd:8e4b%eno1: icmp_seq=1 ttl=64 time=49.1 ms (DUP!)
64 bytes from fe80::9ea0:d783:5e65:e095%eno1: icmp_seq=1 ttl=64 time=52.8 ms (DUP!)
64 bytes from fe80::ce07:e4ff:fe33:5a3a%eno1: icmp_seq=1 ttl=64 time=84.6 ms (DUP!)
64 bytes from fe80::96de:80ff:febf:d656%eno1: icmp_seq=2 ttl=64 time=0.247 ms
What I discovered tonight it is that all servers (even NS6 and NS7) get an IPV6, but my router (openwrt) answers its ipv6 (however no activated dhcp server on IPV6). When I set the ipv6 settings of anaconda to âignoreâ (ânoipv6), I have no problem of bad IPV6 dns entry.
does the --noipv6 can be tricked by kickstart as a default setting ?
the question now is : does this issue is specific to my environment where I have plenty of servers and a (tricky openvz) router or it could be find in others LAN.