From owner-freebsd-stable Sun Sep 23 9:35: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id F064D37B405 for ; Sun, 23 Sep 2001 09:35:03 -0700 (PDT) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id f8NGYwR28149; Sun, 23 Sep 2001 09:34:58 -0700 (PDT) Message-Id: <200109231634.f8NGYwR28149@ptavv.es.net> To: "Juha Saarinen" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: loopback not working for anything other than 127.0.0.1 In-reply-to: Your message of "Sun, 23 Sep 2001 15:08:06 +1200." <000701c143dc$f7331230$0a01a8c0@den2> Date: Sun, 23 Sep 2001 09:34:58 -0700 From: "Kevin Oberman" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > From: "Juha Saarinen" > Date: Sun, 23 Sep 2001 15:08:06 +1200 > Sender: owner-freebsd-stable@FreeBSD.ORG > > :: and note that the only ipv4 address listed is '127.0.0.1'. > > How come it works under Linux? Because the Linux IP stack is horribly broken. (No,this particular item is only stupid as the result of an anomalous reading of an RFC), but the over-all TCP/IP stack in some releases is totally hosed. We recently had a problem with some host flooding one of our OC-3 (155 Mbps) links from a Gig-E system. The traffic was TCP, not UDP, but it totally failed to back off when congestion was encountered, even when ACKs were taking up to 2 seconds to get back to the system, it kept blasting away. Please, please, never use Linux networking as good example! (And please, please, don't use Linux networking on my network.) R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message