From owner-freebsd-net@FreeBSD.ORG Mon Mar 3 12:38:58 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97202106566C for ; Mon, 3 Mar 2008 12:38:58 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (www.tegenbosch28.nl [217.21.251.97]) by mx1.freebsd.org (Postfix) with ESMTP id 55DC68FC2C for ; Mon, 3 Mar 2008 12:38:58 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from localhost (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id 5282D173A3; Mon, 3 Mar 2008 13:38:57 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by localhost (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wDU3IB2LEH7a; Mon, 3 Mar 2008 13:38:55 +0100 (CET) Received: from [212.61.27.67] (opteron.digiware.nl [212.61.27.67]) by mail.digiware.nl (Postfix) with ESMTP id 528C81734E; Mon, 3 Mar 2008 13:38:55 +0100 (CET) Message-ID: <47CBF16C.6020704@digiware.nl> Date: Mon, 03 Mar 2008 13:39:08 +0100 From: Willem Jan Withagen Organization: Digiware User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: =?ISO-8859-2?Q?=A3ukasz_Bromirski?= References: <497111.42659.qm@web63905.mail.re1.yahoo.com> <20080301225727.GA85851@owl.midgard.homeip.net> <47CAADB8.9000202@digiware.nl> <47CC304F.6040006@bromirski.net> In-Reply-To: <47CC304F.6040006@bromirski.net> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit Cc: Barney Cordoba , Ingo Flaschberger , net@freebsd.org Subject: Re: FBSD 1GBit router? 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: Mon, 03 Mar 2008 12:38:58 -0000 Łukasz Bromirski wrote: > Willem Jan Withagen wrote: > >> I'm looking for a stream exploder.:) >> 1 2Mbit stream in, and as many as possible out. >> And 7*1Gb = 14Gbit, so I'd like to be pushing 7000 streams. >> (One advantage is that they will be UDP streams, so there is >> a little less bookkeeping in the protocol stack ) > > Wouldn't it be a case for use of multicast vs unicast? Hardware > is always better anyway, so why not invest in some switch that > can do unicast/multicast in hardware? Usefull suggestion, only this is going to be in an overlay cloud where we do not have control over all the endpoint networks. let alone that we can get them to use multicast. And even those that use multicast in their last-mule equipment, don't always have correct setups. My experience is that Multicast in nice in theory and experiment, but when push comes to shove it does not completely deliver. --WjW