That sounds like old-school: Under traditional "Dual-stack" the intended procedure was indeed first to try IPv6, and only when it fails, THAN to try legacy Ipv4. It was thought that (network) administrators would take their responsibility seriously ;-( Last February, @FOSDEM-RTC-devroom, I was informed that the new V6-mantra is named "Happy Eyes", where both options should be probed simultaneously, And let the first one who succeeds win. <dream> Still, if you get V6 working properly, there's no need for legacy-stuff :-) </dream> -----Original Message----- From: Tim [mailto:ignored_mailbox@xxxxxxxxxxxx] Sent: maandag 10 april 2017 7:39 To: users@xxxxxxxxxxxxxxxxxxxxxxx Subject: Re: Is there a way to stop ipv6 leakage without turning off ipv6? Allegedly, on or about 10 April 2017, Stephen Morris sent: > am I correct in understanding that you are saying that even though I > have IPv6 set to link-local, that IPv6 is still being attempted across > the internet gateway, and in my case because my ISP doesn't support > IPv6, I am assuming those packets would be rejected and hence the > system would fall back to IPv4, or is it the case that > IPv6 is tried for every transmission, which would then make internet > access horribly inefficient? There's a yes and no answer to that, it will depend on the application. I've found that mplayer would first try IPv6, wait for that to fail, then try IPv4, before playing a file. It tries IPv6 because I had IPv6 on my LAN, as far as my router, but my ISP doesn't support IPv6 (so I'd need access to an external gateway). If I totally removed any IPv6 networking from my LAN, it was quicker to start playing streams. Though, the odd thing is that even without IPv6 networking, my DNS server still returns answers for IPv6 addresses (it can still do that through whatever means it has of getting out into the internet). So, to really stop mplayer from always trying IPv6 first, I had to configure mplayer not to do that. Chances are you may have to do that with your browser. Because if anything gives it an IPv6 answer for an address that you're trying to browse (whether that answer comes from your DNS server or a proxy server), it's going to try *it* first. I think that our ISPs are really dragging their heels on this. IPv6 has been around for years, they've been replacing networking equipment for years, it's well past the point where we should have working IPv6 as a matter of course. * In this case the ISP "doesn't support" IPv6 meaning that it's not there, rather than they simply won't give any help with it. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 Boilerplate: All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I only get to see the messages posted to the mailing list. Moments after you've soldered the wires onto the plug just perfectly, you'll realise that you forgot to put the backshell on. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
