From owner-freebsd-net@FreeBSD.ORG Fri Aug 29 03:59:02 2008 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 42C88106564A for ; Fri, 29 Aug 2008 03:59:02 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 92FE38FC19 for ; Fri, 29 Aug 2008 03:59:01 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id m7T3wwDt084955; Fri, 29 Aug 2008 11:58:58 +0800 (KRAST) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id m7T3ww7t084953; Fri, 29 Aug 2008 11:58:58 +0800 (KRAST) (envelope-from eugen) Date: Fri, 29 Aug 2008 11:58:58 +0800 From: Eugene Grosbein To: John Lingate Message-ID: <20080829035858.GA83708@svzserv.kemerovo.su> References: <325689.70498.qm@web58308.mail.re3.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <325689.70498.qm@web58308.mail.re3.yahoo.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org Subject: Re: Quagga OSPF binds to wrong interface on FreeBSD 7 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, 29 Aug 2008 03:59:02 -0000 On Thu, Aug 28, 2008 at 08:19:32PM -0700, John Lingate wrote: > This bug was reported around the release of FreeBSD 7, but does not seem to have made any progress. > > http://bugzilla.quagga.net/show_bug.cgi?id=420 > > Is this because the sockopt.c.diff patch is correct, which isn't entirely clear from the following comments, or is there some other solution to this problem?  Thanks! You should contact with ports/net/quagga maintainer to push temporary patch into Ports Tree until quagga developers settle with something working. This always was most productive way for us. Eugene Grosbein