From owner-freebsd-net@FreeBSD.ORG Thu Jun 19 07:47:19 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 880D737B401 for ; Thu, 19 Jun 2003 07:47:19 -0700 (PDT) Received: from laptop.tenebras.com (laptop.tenebras.com [66.92.188.18]) by mx1.FreeBSD.org (Postfix) with SMTP id 588B743F85 for ; Thu, 19 Jun 2003 07:47:17 -0700 (PDT) (envelope-from kudzu@tenebras.com) Received: (qmail 16873 invoked from network); 19 Jun 2003 14:47:15 -0000 Received: from sapphire.tenebras.com (HELO tenebras.com) (192.168.188.241) by 0 with SMTP; 19 Jun 2003 14:47:15 -0000 Message-ID: <3EF1CCF3.4070506@tenebras.com> Date: Thu, 19 Jun 2003 07:47:15 -0700 From: Michael Sierchio User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, zh-tw, zh-cn, fr, en, de-de MIME-Version: 1.0 To: Hendrik Scholz References: <20030619164024.L698@mcd01p59.mrc.alcatel.ro> <20030619160217.61c77314.hscholz@raisdorf.net> In-Reply-To: <20030619160217.61c77314.hscholz@raisdorf.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org 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: Thu, 19 Jun 2003 14:47:19 -0000 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.