From owner-freebsd-stable Mon Feb 4 6:38: 4 2002 Delivered-To: freebsd-stable@freebsd.org Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id E21DB37B420; Mon, 4 Feb 2002 06:37:59 -0800 (PST) Received: from madman.nectar.cc (madman.nectar.cc [10.0.1.111]) by gw.nectar.cc (Postfix) with ESMTP id 633BF10; Mon, 4 Feb 2002 08:37:59 -0600 (CST) Received: (from nectar@localhost) by madman.nectar.cc (8.11.6/8.11.6) id g14Ebxh29448; Mon, 4 Feb 2002 08:37:59 -0600 (CST) (envelope-from nectar) Date: Mon, 4 Feb 2002 08:37:58 -0600 From: "Jacques A. Vidrine" To: Mike Tancsa Cc: Ruslan Ermilov , stable@FreeBSD.ORG, Warner Losh Subject: Re: dropping 127.* on the floor Message-ID: <20020204143758.GA28243@madman.nectar.cc> References: <20020204152519.B58535@sunbay.com> <3C5DE578.4020409@gmx.net> <20020203152433.A5932-100000@voyager.straynet.com> <3C5DE578.4020409@gmx.net> <5.1.0.14.0.20020204080228.022ab9c0@192.168.0.12> <20020204152519.B58535@sunbay.com> <5.1.0.14.0.20020204092437.050e66e0@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.1.0.14.0.20020204092437.050e66e0@marble.sentex.ca> User-Agent: Mutt/1.3.27i X-Url: http://www.nectar.cc/ 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 On Mon, Feb 04, 2002 at 09:29:08AM -0500, Mike Tancsa wrote: > At 08:12 AM 2/4/02 -0600, Jacques A. Vidrine wrote: > > >See the Bugtraq archives for the thread starting with Message-ID: > ><3AA3ECAB.EA826D28@thebunker.net>, subject ``Loopback and multi-homed > >routing flaw in TCP/IP stack.'' for the reasons behind this change. > >The following URL might work. > > > > > > What if this were dealt as part of firewall rules ? i.e. GENERIC was built > by default with IPFIREWALL and firewall_enable="YES" and > firewall_type="OPEN" were set. That way the behavior that people have come > to rely on is still there for those that need it. > > I have not tested this yet with my production transparent proxies but I > will try so later today to see if the behavior is broken as a number of > people have reported. We are talking about two different things: ip_input.c and ip_output.c. The recent change to ip_output.c is what might break your transparent proxy. Above I am talking about the year-old change to ip_input.c. Cheers, -- Jacques A. Vidrine http://www.nectar.cc/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos jvidrine@verio.net . nectar@FreeBSD.org . nectar@kth.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message