| 1 |
On Friday, 13 October 2017 22:55:50 BST Daniel Frey wrote: |
| 2 |
> On 10/13/2017 02:48 PM, Grant Edwards wrote: |
| 3 |
> > On 2017-10-13, Vadim A. Misbakh-Soloviov <gentoo@×××.name> wrote: |
| 4 |
> >> Well, actually, you was alread adviced about some working methods of |
| 5 |
> >> solving your issue (both right and wrong ones, but it is anyway your |
| 6 |
> >> decision to take ones to use), so I'll just clarify the simple |
| 7 |
> >> thing: |
| 8 |
> >> |
| 9 |
> >> You can suffer on such problems in relation to IPv6 **ONLY** in the |
| 10 |
> >> case when your ISP **DO** have IPv6 support (say, announce IPv6 |
| 11 |
> >> preffix to you via SLAAC or DHCPv6), but having **BROKEN** IPv6 |
| 12 |
> >> routing. |
| 13 |
> > |
| 14 |
> > It might not be the ISP that's broken. It might be the user's |
| 15 |
> > firewall/router. A lot of the cheap consumer models are starting to |
| 16 |
> > "support" IPv6 by default when it appears to them that the ISP |
| 17 |
> > supports IPv6. But, the default IPv6 firewall/router settings aren't |
| 18 |
> > always usable. |
| 19 |
> |
| 20 |
> I'm currently using the ISP provided router, as I don't have anything |
| 21 |
> ATM that can handle 150 mbps symmetrical. |
| 22 |
> |
| 23 |
> Dan |
| 24 |
|
| 25 |
I'm guessing the delay is due to DNS resolution missing of being misconfigured |
| 26 |
somewhere in your/your ISPs network. Could you tweak your router's DNS |
| 27 |
resolver addresses to point to OpenDNS resolvers, or some such if your ISP's |
| 28 |
are not working properly? |
| 29 |
|
| 30 |
-- |
| 31 |
Regards, |
| 32 |
Mick |
Archives