Date: Mon, 04 Feb 2002 09:29:08 -0500 From: Mike Tancsa <mike@sentex.net> To: "Jacques A. Vidrine" <n@nectar.cc>, Ruslan Ermilov <ru@FreeBSD.ORG> Cc: stable@FreeBSD.ORG, Warner Losh <imp@FreeBSD.ORG> Subject: Re: dropping 127.* on the floor Message-ID: <5.1.0.14.0.20020204092437.050e66e0@marble.sentex.ca> In-Reply-To: <20020204141227.GB23733@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > ><URL:http://www.securityfocus.com/cgi-bin/archive.pl?id=1&mid=3AA3ECAB.EA826D28@thebunker.net>; 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. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.1.0.14.0.20020204092437.050e66e0>