From owner-freebsd-net@FreeBSD.ORG Mon Apr 26 07:56:41 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1DC316A4CE for ; Mon, 26 Apr 2004 07:56:41 -0700 (PDT) Received: from grosbein.pp.ru (grgw.svzserv.kemerovo.su [213.184.64.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9627443D58 for ; Mon, 26 Apr 2004 07:56:40 -0700 (PDT) (envelope-from eugen@grosbein.pp.ru) Received: from grosbein.pp.ru (eugen@localhost [127.0.0.1]) by grosbein.pp.ru (8.12.11/8.12.11) with ESMTP id i3QEubpb000628; Mon, 26 Apr 2004 22:56:37 +0800 (KRAST) (envelope-from eugen@grosbein.pp.ru) Received: (from eugen@localhost) by grosbein.pp.ru (8.12.11/8.12.11/Submit) id i3QEubpG000627; Mon, 26 Apr 2004 22:56:37 +0800 (KRAST) (envelope-from eugen) Date: Mon, 26 Apr 2004 22:56:37 +0800 From: Eugene Grosbein To: Mike Tancsa Message-ID: <20040426145637.GB398@grosbein.pp.ru> References: <20040422130659.GG722@empiric.dek.spc.org> <408CA012.AF5018B@kuzbass.ru> <6.0.3.0.0.20040426104224.09809978@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.0.3.0.0.20040426104224.09809978@64.7.153.2> User-Agent: Mutt/1.4.1i cc: freebsd-net@freebsd.org Subject: Re: BGP MD5: compatibility for STABLE? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2004 14:56:42 -0000 On Mon, Apr 26, 2004 at 10:45:21AM -0400, Mike Tancsa wrote: > >Are there corresponding patches for routing daemons available to public? > > The links were posted a few times. The keywords "bgp md5 quagga freebsd > patches" in google first link points to > http://lists.quagga.net/pipermail/quagga-users/2004-February/001469.html > which has the links to what you are after. Thank you very much, I'll go for it. It would be nice if patches where in the ports tree until they included in the vendor distribution. That is what ports are for, aren't they? Eugene