From owner-freebsd-net@FreeBSD.ORG Fri Sep 25 07:37:40 2009 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C1F51065693; Fri, 25 Sep 2009 07:37:40 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id 815928FC1C; Fri, 25 Sep 2009 07:37:40 +0000 (UTC) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n8P7ZrTx024235; Fri, 25 Sep 2009 00:37:40 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 25 Sep 2009 00:27:04 -0700 Message-ID: In-Reply-To: <4ABC6E7C.80305@FreeBSD.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Point-to-Point interfaces regressions Thread-Index: Aco9sD+8nsqzA6lWTl2WknIwkaHU9wAAFjSQ References: <4ABBAC87.4040306@FreeBSD.org> <4ABBE5C6.6070707@FreeBSD.org> <4ABC6E7C.80305@FreeBSD.org> From: "Li, Qing" To: "Alexander Motin" Cc: freebsd-net , freebsd-current@FreeBSD.org Subject: RE: Point-to-Point interfaces regressions X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2009 07:37:40 -0000 >=20 > Li, Qing wrote: > >> Me and many other people running net/mpd handling thousands of PtP > >> interfaces sharing local addresses with each other and with some > >> Ethernet interface. This change makes such setup inoperable, as mpd > >> will constantly receive errors while trying to set addresses and > >> drop connections. > > > > I can revert to the old behavior. I asked for feedback and received > > none at the time ... >=20 > I would like to see it working, but working correctly. If it is not > possible to implement it correctly - then reverted, or at least > disabled > by default. >=20 Asking for compatibility is reasonable but the existing packet=20 leaking behavior is incorrect. =20 After reviewing the previous thread on this topic back in July, I see that Henri Hennebert requested this feature for IPv6. I intend to introduce a sysctl variable to control whether loopback route should be installed for the local end point. By default the old behavior maintained. -- Qing