Ask Your Question

Revision history [back]

So, I ran dnf upgrade this morning, there was an upgrade to dnsmasq - dnsmasq.x86_64.2.76-5.fc26

Voila, I do not have to disable ipv6 on my interface to access fedoraproject.org or other sites that show ipv6 addresses and ipv4 address with nslookup. My ifconfig shows my active network interface configured for both ipv4 and ipv6 and ping gets an ipv4 address.

My take on this is that the weak ipv6 points in the Internet are software and network devices that can not yet handle ipv6. Much has been written about ipv6's packet segmentation which is entirely different from ipv4's approach and its negative effect on software that accommodates both ipv4 and ipv6.

So, I ran dnf upgrade this morning, there was an upgrade to dnsmasq - dnsmasq.x86_64.2.76-5.fc26

Voila, I do not have to disable ipv6 on my interface to access fedoraproject.org or other sites that show ipv6 addresses and ipv4 address with nslookup. My ifconfig shows my active network interface configured for both ipv4 and ipv6 and ping gets an ipv4 address.

My take on this is that the weak ipv6 points in the Internet are software and network devices that can not yet handle ipv6. Much has been written about ipv6's packet segmentation which is entirely different from ipv4's approach and its negative effect on software that accommodates both ipv4 and ipv6.

Here is a link describing dnsmasq problems as of October 3, 2017 - https://www.helpnetsecurity.com/2017/10/03/dnsmasq-flaws/