From: Gregory Maxwell <greg@linuxpower.cx>
To: Chris Wedgwood <cw@f00f.org>
Cc: CaT <cat@zip.com.au>, "David S. Miller" <davem@redhat.com>,
"James H. Cloos Jr." <cloos@jhcloos.com>,
linux-kernel@vger.kernel.org
Subject: Re: hotmail can't deal with ECN
Date: Fri, 26 Jan 2001 08:09:09 -0500 [thread overview]
Message-ID: <20010126080909.A5277@xi.linuxpower.cx> (raw)
In-Reply-To: <14960.29127.172573.22453@pizda.ninka.net> <200101251905.f0PJ5ZG216578@saturn.cs.uml.edu> <14960.31423.938042.486045@pizda.ninka.net> <20010125115214.D9992@draco.foogod.com> <m3itn3i5iu.fsf@austin.jhcloos.com> <14960.50897.494908.316057@pizda.ninka.net> <20010126115057.A366@zip.com.au> <20010126221414.E11097@metastasis.f00f.org>
In-Reply-To: <20010126221414.E11097@metastasis.f00f.org>; from cw@f00f.org on Fri, Jan 26, 2001 at 10:14:14PM +1300
On Fri, Jan 26, 2001 at 10:14:14PM +1300, Chris Wedgwood wrote:
> On Fri, Jan 26, 2001 at 11:50:57AM +1100, CaT wrote:
>> *screatches head*
>>
>> I'm not sure as to what the problem with hotmail may be. I have ECN
>> turned on:
>>
>> gozer:~# more /proc/sys/net/ipv4/tcp_ecn
>> 1
>>
>> and I can contact hotmail just fine. I also can ftp to your site
>> non-passively. where should I go to on hotmail to see it fail?
>
> Your ISP probably transparently proxies/caches your http sessions...
Anyone know the person at AOL responcible for their proxy?
I bet I know a way to get ECN fixed once and for all. (It's not like AOL
would lose users over it... Their tech support is already very skilled at
telling people it's the remote site's fault. :) ).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-26 13:09 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 18:29 hotmail can't deal with ECN Jeremy Hansen
2001-01-25 18:34 ` David S. Miller
2001-01-25 19:05 ` Albert D. Cahalan
2001-01-25 19:13 ` David S. Miller
2001-01-25 19:29 ` Jeremy Hansen
2001-01-25 19:30 ` mirabilos
2001-01-25 19:52 ` alex
2001-01-25 20:13 ` mirabilos
2001-01-26 8:56 ` Helge Hafting
2001-01-25 23:19 ` James H. Cloos Jr.
2001-01-26 0:37 ` David S. Miller
2001-01-26 0:50 ` CaT
2001-01-26 0:59 ` Jan Niehusmann
2001-01-26 1:03 ` CaT
2001-01-31 16:13 ` Alan Cox
2001-01-26 1:04 ` David S. Miller
2001-01-26 1:08 ` CaT
2001-01-26 10:04 ` James Sutherland
2001-01-26 9:14 ` Chris Wedgwood
2001-01-26 13:09 ` Gregory Maxwell [this message]
2001-01-26 2:55 ` Steven N. Hirsch
2001-01-26 6:51 ` Michael B. Trausch
2001-01-26 23:44 ` Thunder from the hill
2001-01-29 13:54 ` Thunder from the hill
2001-01-30 7:21 ` Michael B. Trausch
2001-01-30 7:35 ` H. Peter Anvin
2001-01-30 7:44 ` David S. Miller
2001-01-30 8:51 ` Michael B. Trausch
2001-01-30 9:33 ` H. Peter Anvin
2001-01-30 9:54 ` Michael B. Trausch
2001-01-26 9:15 ` Chris Wedgwood
2001-01-26 12:51 ` Steven N. Hirsch
2001-01-26 13:10 ` Gregory Maxwell
2001-01-26 9:12 ` Chris Wedgwood
2001-01-26 11:37 ` David S. Miller
2001-01-27 0:13 ` Thunder from the hill
2001-01-26 9:29 ` Helge Hafting
-- strict thread matches above, loose matches on Subject: below --
2001-02-02 9:17 Sam James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010126080909.A5277@xi.linuxpower.cx \
--to=greg@linuxpower.cx \
--cc=cat@zip.com.au \
--cc=cloos@jhcloos.com \
--cc=cw@f00f.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox