From: CaT <cat@zip.com.au>
To: Jan Niehusmann <jan@gondor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: hotmail can't deal with ECN
Date: Fri, 26 Jan 2001 12:03:12 +1100 [thread overview]
Message-ID: <20010126120312.C366@zip.com.au> (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> <20010126015901.A19138@gondor.com>
In-Reply-To: <20010126015901.A19138@gondor.com>; from jan@gondor.com on Fri, Jan 26, 2001 at 01:59:01AM +0100
On Fri, Jan 26, 2001 at 01:59:01AM +0100, Jan Niehusmann wrote:
> On Fri, Jan 26, 2001 at 11:50:57AM +1100, CaT wrote:
> > 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?
>
> You may be located behind a firewall that zeroes out the ECN bits. This would
> mean that hotmail doesn't get ECN packets and the connection gets established
> just as if you were talking to a plain non-ECN server without a firewall.
gozer IS my firewall. :) beyond it is a modem and a dailup point, my ISPs
LAN and then the innanet. and I tried from it and from a box behind it.
I connected to hotmail just fine.
still, any way to test if the ECN bits are going through just fine?
--
CaT (cat@zip.com.au) *** Jenna has joined the channel.
<cat> speaking of mental giants..
<Jenna> me, a giant, bullshit
<Jenna> And i'm not mental
- An IRC session, 20/12/2000
-
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 1:03 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 [this message]
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
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=20010126120312.C366@zip.com.au \
--to=cat@zip.com.au \
--cc=jan@gondor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.