From owner-freebsd-net@FreeBSD.ORG Fri May 19 07:54:01 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 14B5416A42F for ; Fri, 19 May 2006 07:54:01 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from conversation.bsdunix.ch (ns1.bsdunix.ch [82.220.17.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88F5643D46 for ; Fri, 19 May 2006 07:54:00 +0000 (GMT) (envelope-from freebsdlists@bsdunix.ch) Received: from localhost (localhost.bsdunix.ch [127.0.0.1]) by conversation.bsdunix.ch (Postfix) with ESMTP id 470AD61D9; Fri, 19 May 2006 09:55:54 +0200 (CEST) X-Virus-Scanned: by amavisd-new at mail.bsdunix.ch Received: from conversation.bsdunix.ch ([127.0.0.1]) by localhost (conversation.bsdunix.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id CAtsCPQFSwUi; Fri, 19 May 2006 09:55:53 +0200 (CEST) Received: from bert.mlan.solnet.ch (bert.mlan.solnet.ch [212.101.1.83]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by conversation.bsdunix.ch (Postfix) with ESMTP id 89BC761D3; Fri, 19 May 2006 09:55:53 +0200 (CEST) From: Thomas To: Julian Elischer In-Reply-To: <446D19E7.2010804@elischer.org> References: <20060518220945.f81a743a.lists@yazzy.org> <446D19E7.2010804@elischer.org> Content-Type: text/plain Date: Fri, 19 May 2006 09:53:57 +0200 Message-Id: <1148025237.38606.6.camel@bert.mlan.solnet.ch> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 SolNet.ch ISP Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Marcin Jessa Subject: Re: trunk interface (was (no subject)) 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, 19 May 2006 07:54:01 -0000 Am Donnerstag, den 18.05.2006, 18:05 -0700 schrieb Julian Elischer: > Thomas Vogt wrote: > > > Hi > > > > Thanks. I know about the netgraph ether/fec interfaces. But I thought > > about a solution without netgraph. AFAIK Netgraph implies overhead > > and ng_ehter is more complicated to set up. This is a problem with > > non technical people. I'm happy they already know a bit about > > ifconfig commands. > > > two items. > 1/ ng_fec only uses the config framework of netgraph. For data it goes > direct to the interfaces. Ah good to know. Since this is for a network course it would be easier if this "trunk" could be setup via ifconfig command. But I will try it. > 2/ netgraph is not that high an overhead. (what made you think it was?) Well I heard that netgraph has some overhead on various conferences. I'm planning to use such a feature on very very high loaded GigE router, every extra kernel hook could cost some performance, IMHO. Thanks and cheers, Thomas