| 1 |
On Sat, 20 Nov 2010 00:32:28 -0500, Walter Dnes wrote: |
| 2 |
|
| 3 |
> > But harmless. The severe delays you noticed were the result of a |
| 4 |
> > broken modem/router failing to recognise that IPv6 was not available |
| 5 |
> > and trying to use it anyway. The usual fix for such a problem is a |
| 6 |
> > firmware update. |
| 7 |
> |
| 8 |
> It's more complex than that. How is the IPV6-enabled browser or media |
| 9 |
|
| 10 |
It's not the browser, its the resolver, the delays are caused by |
| 11 |
excessively long DNS lookups. |
| 12 |
|
| 13 |
> player supposed to know that my modem doesn't support IPV6 |
| 14 |
|
| 15 |
The modem tells it and the resolver falls back to IPv4. The problem |
| 16 |
occurs when the modem doesn't know that it doesn't support IPv6 (or even |
| 17 |
what IPv6 is, which is why a firmware update usually fixes it) so the |
| 18 |
resolver doesn't try IPv4 until the IPv6 request times out. |
| 19 |
|
| 20 |
Using 21st Century software with 20th Century hardware is asking for such |
| 21 |
problems :( |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Neil Bothwick |
| 26 |
|
| 27 |
I am McCoy of Bo...Damnit! I'm a doctor, not a collective! |
Archives