>However, web browsing sucks. On about 80% of all links, there is a noticable
>hesitation, between 1-15 seconds, as it looks up the name and as it fetches
>the first page. After that point, that site will appear to be OK.
This means, that 80% of all web site operators are too dumb to
configure a web server. Is it possible that your brand spanking new T1
addresses have no reverse name resolution? Are you using a proxy?
Look:
lm@bitmover IP 1.2.3.4
|
|
"i want to surf to http://www.surf.xxx/"
|
|
v
Website "www.surf.xxx"
"connect from 1.2.3.4" -> "Lookup for 4.3.2.1.IN-ADDR.ARPA"
|
|
1-15 Second timeout, "addr not found"
|
|
v
send HTTP page to 1.2.3.4 anyway.
>Before I wander off to write a test for this, I'm wondering if anyone
>knows of a test suite or a methodology which works. I was thinking
This has nothing to do with OSes, Linux or even a kernel. It is just
that most people on this net (and also most people who operate servers
or work at ISPs) are complete idiots that neither know how to operate
a webserver (set it to "name lookup off" and do address resolving for
web statistics offline) or an ip-space (how to setup a reverse
resolution).
I did consulting for an ISP that has > 50 Class C networks and not
_one_ had right forward and reverse resolution [1] as I arrived there.
Regards
Henning
[1] Now it has. ;-)
-- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.deAm Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de D-91054 Buckenhof Fax.: 09131 / 50654-20 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/