On Mon, July 28 at  1:04 AM EDT
Greg Folkert <[EMAIL PROTECTED]> wrote:

>On Mon, 2003-07-28 at 00:43, Ron Johnson wrote:
><---SNIP--->
>> # cat /proc/sys/net/ipv4/tcp_ecn
>> 1
>> 
>> When /proc/sys/net/ipv4/tcp_ecn had the value "1", I couldn't get 
>> to thatpetplace either.  However, I could, after I did this, and
>> then restarted Mozilla:
>> # echo "0" > /proc/sys/net/ipv4/tcp_ecn
>> # cat /proc/sys/net/ipv4/tcp_ecn
>> 0
>> 
>> Make sure to reenable tcp_ecn when you're finished!
>> 
>> # echo "1" > /proc/sys/net/ipv4/tcp_ecn
>> # cat /proc/sys/net/ipv4/tcp_ecn
>> 1
>
>Ron, as of this writing, 12:55AM EDT, I will have to disagree with you
>about turning tcp_ecn back on. For about the next 2 years at least.
>
...
<--SNIPPED-->
...
>Well, overall ECN is a great way to make the Internet "self-regulate"
>and of course the biggest obstacle is M$ products. But for quite a
>while yet, defaulting it to OFF is a good thing.

Could one of you briefly describe ECN and/or point me to a link?  I
have never heard of it.


Shawn Lamson
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to