From owner-freebsd-net@FreeBSD.ORG  Mon Mar  8 20:04:59 2004
Return-Path: <owner-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 AE24C16A4CE
	for <freebsd-net@freebsd.org>; Mon,  8 Mar 2004 20:04:59 -0800 (PST)
Received: from bes.amduat.net (bes.amduat.net [206.124.149.190])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4A6B743D31
	for <freebsd-net@freebsd.org>; Mon,  8 Mar 2004 20:04:59 -0800 (PST)
	(envelope-from jbarrett@amduat.net)
Received: from osiris.amduat.net (osiris.amduat.net [10.0.0.69])
  (AUTH: LOGIN jbarrett, SSL: TLSv1/SSLv3,128bits,RC4-MD5)
  by bes.amduat.net with esmtp; Mon, 08 Mar 2004 20:04:58 -0800
From: "Jacob S. Barrett" <jbarrett@amduat.net>
To: "Will Saxon" <WillS@housing.ufl.edu>
Date: Mon, 8 Mar 2004 14:16:30 -0800
User-Agent: KMail/1.6
References: <0E972CEE334BFE4291CD07E056C76ED802E867D7@bragi.housing.ufl.edu>
In-Reply-To: <0E972CEE334BFE4291CD07E056C76ED802E867D7@bragi.housing.ufl.edu>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200403081416.30233.jbarrett@amduat.net>
cc: eberkut@minithins.net
cc: freebsd-net@freebsd.org
Subject: Re: Solution for Resilient VLAN Trunk Bonding
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2004 04:04:59 -0000

On Monday 08 March 2004 01:41 pm, Will Saxon wrote:
> Regardless, it doesn't look like ng_fec can work with ng_vlan, since
> it doesn't provide any hooks to work with.

Couldn't you attach ng_vlan downstream to the ng_ether lower that will created 
for the ng_fec interface?

-- 
Jacob S. Barrett
jbarrett@amduat.net
www.amduat.net

"I don't suffer from insanity, I enjoy every minute of it."