From owner-freebsd-net@FreeBSD.ORG Thu Jun 19 22:53:54 2003 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 43A8137B404 for ; Thu, 19 Jun 2003 22:53:54 -0700 (PDT) Received: from smail2.alcatel.fr (colt-na7.alcatel.fr [62.23.212.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 906E843F75 for ; Thu, 19 Jun 2003 22:53:52 -0700 (PDT) (envelope-from ciprian.badescu@alcatel.ro) Received: from ns.tm.alcatel.ro (ns.tm.alcatel.ro [155.132.154.34]) by smail2.alcatel.fr (ALCANET/NETFR) with SMTP id h5K5rpdk019758 for ; Fri, 20 Jun 2003 07:53:51 +0200 Received: FROM mail.tm.alcatel.ro BY ns.tm.alcatel.ro ; Fri Jun 20 08:55:56 2003 +0300 Received: from mrc.mrc.alcatel.ro (unverified [172.25.128.124]) by mail.tm.alcatel.ro (EMWAC SMTPRS 0.83) with SMTP id ; Fri, 20 Jun 2003 08:55:19 +0300 Received: from mcd01paf (mcd01paf.mrc.alcatel.ro [172.25.128.175]) h5K644Nr009980 for ; Fri, 20 Jun 2003 09:04:04 +0300 (EEST) Date: Fri, 20 Jun 2003 08:59:29 +0300 (EEST) From: Ciprian Badescu X-X-Sender: badescu@mcd01p59.mrc.alcatel.ro To: freebsd-net@freebsd.org In-Reply-To: <3EF1CCF3.4070506@tenebras.com> Message-ID: <20030620084923.Y12785@mcd01p59.mrc.alcatel.ro> References: <20030619160217.61c77314.hscholz@raisdorf.net> <3EF1CCF3.4070506@tenebras.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new Subject: Re: Redundant link configuration 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: Fri, 20 Jun 2003 05:53:54 -0000 I agree, the weight parameter is also what I need;) but I ask again: It isn't possible to solve this at a higher level (routing) ? There is the 'metric' option for routes, I can put a bigger metric for the backup link. Will this link be automatically used when the primary link with a lower metric is down? Or RIP running on both routers can be a solution for this? thanks -- Ciprian Badescu On Thu, 19 Jun 2003, Michael Sierchio wrote: > Date: Thu, 19 Jun 2003 07:47:15 -0700 > From: Michael Sierchio > To: Hendrik Scholz > Cc: freebsd-net@freebsd.org > Subject: Re: Redundant link configuration > > Hendrik Scholz wrote: > > > Have a look at the ng_one2many module. The manpage comes with a nice > > example and offers the needed featuers. > > NG_ONE2MANY(4) > > TRANSMIT ALGORITHMS > At this time, the only algorithm for determing the outgoing many hook is > a simple round-robin delivery algorithm. Packets are delivered out the > many hooks in sequential order. > > In the future other algorithms may be added as well. > > That would be nice -- in particular, links with different > characteristic capacities and latencies would be nice to bond -- > as in a shared DS3 and a 256kb frame relay, my current problem. > > We have an expensively idle backup frame relay link which could > be carrying "stuff" -- even simple parameters such as weighted > preference would suffice. > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >