On 10/14/2017 04:05 AM, Mick wrote:
On Friday, 13 October 2017 22:55:50 BST Daniel Frey wrote:
On 10/13/2017 02:48 PM, Grant Edwards wrote:
On 2017-10-13, Vadim A. Misbakh-Soloviov <gen...@mva.name> wrote:
Well, actually, you was alread adviced about some working methods of
solving your issue (both right and wrong ones, but it is anyway your
decision to take ones to use), so I'll just clarify the simple
thing:
You can suffer on such problems in relation to IPv6 **ONLY** in the
case when your ISP **DO** have IPv6 support (say, announce IPv6
preffix to you via SLAAC or DHCPv6), but having **BROKEN** IPv6
routing.
It might not be the ISP that's broken. It might be the user's
firewall/router. A lot of the cheap consumer models are starting to
"support" IPv6 by default when it appears to them that the ISP
supports IPv6. But, the default IPv6 firewall/router settings aren't
always usable.
I'm currently using the ISP provided router, as I don't have anything
ATM that can handle 150 mbps symmetrical.
Dan
I'm guessing the delay is due to DNS resolution missing of being misconfigured
somewhere in your/your ISPs network. Could you tweak your router's DNS
resolver addresses to point to OpenDNS resolvers, or some such if your ISP's
are not working properly?
No, the DNS was working. It was trying to connect to a specific ipv6
address to sync, and failing (twice.)
That's what I initially thought too, but checked name resolution and it
was returning proper addresses.
I even thought (before I started to remove systemd from my old laptop) I
could save time by disabling ipv6 on the ISP router (my cell phone
suffers the same delay), but then it wouldn't even connect to their network.
Dan
