From owner-freebsd-net@FreeBSD.ORG Tue May 26 14:50:03 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D321106566B for ; Tue, 26 May 2009 14:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1A3618FC1E for ; Tue, 26 May 2009 14:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4QEo2gl053561 for ; Tue, 26 May 2009 14:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4QEo2Zs053560; Tue, 26 May 2009 14:50:02 GMT (envelope-from gnats) Date: Tue, 26 May 2009 14:50:02 GMT Message-Id: <200905261450.n4QEo2Zs053560@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Mark Linimon Cc: Subject: Re: kern/134931: [route] [fib] Route messages sent to all socket listeners regardless of setfib X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Linimon List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 14:50:03 -0000 The following reply was made to PR kern/134931; it has been noted by GNATS. From: Mark Linimon To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/134931: [route] [fib] Route messages sent to all socket listeners regardless of setfib Date: Tue, 26 May 2009 09:43:41 -0500 ----- Forwarded message from Bruce Simpson ----- From: Bruce Simpson To: linimon@FreeBSD.org CC: freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org Subject: Re: kern/134931: [route] [fib] Route messages sent to all socket listeners regardless of setfib linimon@FreeBSD.org wrote: > Synopsis: [route] [fib] Route messages sent to all socket listeners regardless of setfib > That might actually be a feature, however, the "API contract" with the multiple routing table support might not have covered this, so it might be "undefined behaviour". ----- End forwarded message -----