mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gerhard Mack <gmack@innerfire.net>
To: "Steven N. Hirsch" <shirsch@adelphia.net>
Cc: Helge Hafting <helgehaf@idb.hist.no>,
	Nicolas Noble <Pixel@the-babel-tower.nobis.phear.org>,
	linux-kernel@vger.kernel.org
Subject: Re: kernel network problem ?
Date: Tue, 9 Jan 2001 08:06:37 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.10.10101090802060.22357-100000@innerfire.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0101090853250.27322-100000@pii.fast.net>

On Tue, 9 Jan 2001, Steven N. Hirsch wrote:

> On Tue, 9 Jan 2001, Helge Hafting wrote:
> 
> > Nicolas Noble wrote:
> > [...]
> > As others have told already, this is the ECN problem.
> > 
> > > I noticed the same bug. This is very weired, I can send a list of sites
> > > which I can't connect anymore. 
> > 
> > You have a list?  Send all of them a message stating that they ought
> > to upgrade their firewalls which cause this problem.  Or they
> > will loose customers/visitors.  Cisco already have an upgrade for them,
> > so fixing is dead easy, and they can then boast compatibility with
> > the latest internet standards.  
> > 
> > If they don't care about linux users, tell them that windows eventually
> > will use ECN too.  They definitely don't want to have a ECN problem when
> > that happens.
> 
> After upgrading to kernel 2.4.0, I found myself unable to retrieve mail
> from Adelphia's (2-way cable ISP) POP server.  It took several days to
> figure out that _one_ of their routers was configured to block ECN.  After
> bringing this to the attention of their network engineers, I was informed
> that their policy prohibits making any router changes on the basis of one
> trouble report.  The person I spoke with did NOT try to defend their
> setup, but it was made clear that they'll do nothing until Windows breaks.
> 
> If I were packaging a Linux distribution, I'd be sure to have ECN disabled
> by default, FWIW.
> 

It's not a matter of changing network setup... if those are cisco routers
there are patches to fix the bugs.

Here is what little info I have on the topic (shamelessly ripped from an
earlier email by "Dax Kelson <dax@gurulabs.com>" )


Here is the fix for PIX:
http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCds23698

    Bud ID:        CSCds23698
    Headline:      PIX sends RSET in response to tcp connections with ECN
 bits set
    Product:       PIX
    Component:     fw
    Severity:      2            Status:           R [Resolved]
    Version Found: 5.1(1)       Fixed-in Version: 5.1(2.206) 5.1(2.207)
 5.2(1.200)

Here is the fix for Local Director:
http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCds40921

Bug Id : CSCds40921
 Headline:  LD rejects syn with reserved bits set in flags field of TCP
hdr
 Product:  ld
 Component: rotor
 Severity: 3                     Status:        R [Resolved]
 Version Found: 3.3(3)           Fixed-in Version: 3.3.3.107


--
Gerhard Mack

gmack@innerfire.net

<>< As a computer I find your faith in technology amusing.



-
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/

  parent reply	other threads:[~2001-01-09 16:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05 14:34 Nicolas Parpandet
2001-01-05 15:42 ` Matti Aarnio
2001-01-05 15:58   ` Nicolas Noble
2001-01-05 15:42 ` Mathieu Chouquet-Stringer
2001-01-05 19:31   ` Graham Murray
2001-01-05 15:49 ` Nicolas Noble
2001-01-09  9:37   ` Helge Hafting
2001-01-09 13:57     ` Steven N. Hirsch
2001-01-09 13:32       ` Alan Cox
2001-01-09 13:46         ` Gregory Maxwell
2001-01-10  7:55         ` Nicolas Parpandet
2001-01-09 16:06       ` Gerhard Mack [this message]
2001-01-05 15:49 ` Richard Rak
2001-01-05 15:55 ` Nicolas Noble
2001-01-05 23:38 ` J Sloan

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=Pine.LNX.4.10.10101090802060.22357-100000@innerfire.net \
    --to=gmack@innerfire.net \
    --cc=Pixel@the-babel-tower.nobis.phear.org \
    --cc=helgehaf@idb.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shirsch@adelphia.net \
    /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

all inboxes | Powered by JetHome®