From: Stefan Traby <stefan@hello-penguin.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: stefan@hello-penguin.com, Andi Kleen <ak@suse.de>,
Dave <daveo@osdn.com>,
linux-kernel@vger.kernel.org
Subject: Re: bizarre TCP behavior
Date: Fri, 20 Apr 2001 11:36:06 +0200 [thread overview]
Message-ID: <20010420113606.A1113@stefan.sime.com> (raw)
In-Reply-To: <20010414141208.A31782@stefan.sime.com> <E14oR1o-00051n-00@the-village.bc.nu>
In-Reply-To: <E14oR1o-00051n-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sat, Apr 14, 2001 at 03:27:53PM +0100
On Sat, Apr 14, 2001 at 03:27:53PM +0100, Alan Cox wrote:
> > For example the Zyxel 681 SDSL-Router breaks ECN by
> > stripping 0x80 (ECN Cwnd Reduced) but not 0x40 (ECN Echo)
> > (TOS bits) on all SYN packets (!).
> >
> > I complained because of this two times more than a month ago
> > but they do not even respond.
>
> If the router claims to be RFC compliant then you may want to investigate
> trading standards bodies. In the UK at least things like the advertising
> standards agency get upset by people who claim standards compliance, are shown
> not to be compliant and are not fixing things..
FYI: I just tested a beta firmare that does not break ECN.
(ZyXEL firmware v2.50(T.05)b6 | 03/28/2001)
I hope that Zyxel will make a release soon, the last official firmare
does not support it. (Ahm, people that are willing to upgrade should
do it on _both_ sides)
--
ciao -
Stefan
prev parent reply other threads:[~2001-04-20 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 22:24 bizarre TCP behavior Dave
2001-04-10 22:56 ` Gregory Maxwell
2001-04-10 23:01 ` Dave
2001-04-11 0:21 ` Andi Kleen
2001-04-11 0:35 ` Mike Castle
2001-04-11 1:06 ` Andi Kleen
2001-04-14 12:12 ` Stefan Traby
2001-04-14 14:27 ` Alan Cox
2001-04-14 22:54 ` Dan Hollis
2001-04-20 9:36 ` Stefan Traby [this message]
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=20010420113606.A1113@stefan.sime.com \
--to=stefan@hello-penguin.com \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=daveo@osdn.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