Did you make the kernel with IP: Explicit Congestion Notification
support turned on? If you did that explains it. Broken routers on the
net make this a bad option to use.

Cheers,

Davidm

On Fri, 2002-12-06 at 18:38, Ed Skinner wrote:
>      Briefly, with 2.4.19 I can't get to certain web locations while other 
> locations work just fine. I see the problems with plain ftp, mozilla and with 
> lynx.
>      Not so briefly:
>      I upgraded my kernel (compiled from source, etc.) to 2.4.19 about two 
> weeks ago. Everything seemed to be working but yesterday I noticed I could 
> not access some web and ftp locations. After suffering the "You're not 
> running Windows?" discussion with Qwest technical support, I was embarassed 
> to notice that other systems here worked fine. The problem was limited to the 
> one machine. I sheepishly told the Qwest technician "never mind" and started 
> trying to debug the situation.
>      A few minutes ago I rebooted that machine with the previous kernel, 
> 2.4.9_34, and found those same locations now working. In 2.4.9_34 it works, 
> in 2.4.19 it fails, but only for selected web locations. For what it may be 
> worth, the failing/working web locations are www.users.qwest.net and 
> ftp.users.qwest.net.
>      Anyone recognize what's wrong or know where I should go to research this?
>      Any/all tips/suggestions would be most welcome. I'm looking for 1) a 
> fix, and 2) a methodology to resolve this on my own next time. (I'd 
> appreciate both a fish, and being taught how to fish.)
>      TIA
-- 
David IS Mandala
gpg fingerprint 8932 E7EF CCF5 1B8C 1B5C  A92E C678 795E 45B2 D952
Phoenix, AZ (480) 460-7546 HP, (602) 321-8277 CP
http://www.them.com/~davidm/