Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 Sep 2009 00:27:04 -0700
From:      "Li, Qing" <qing.li@bluecoat.com>
To:        "Alexander Motin" <mav@FreeBSD.org>
Cc:        freebsd-net <freebsd-net@FreeBSD.org>, freebsd-current@FreeBSD.org
Subject:   RE: Point-to-Point interfaces regressions
Message-ID:  <B583FBF374231F4A89607B4D08578A4305699AA6@bcs-mail03.internal.cacheflow.com>
In-Reply-To: <4ABC6E7C.80305@FreeBSD.org>
References:  <4ABBAC87.4040306@FreeBSD.org> <B583FBF374231F4A89607B4D08578A430569985B@bcs-mail03.internal.cacheflow.com> <4ABBE5C6.6070707@FreeBSD.org> <B583FBF374231F4A89607B4D08578A43056998A4@bcs-mail03.internal.cacheflow.com> <4ABC6E7C.80305@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
>=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





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B583FBF374231F4A89607B4D08578A4305699AA6>