From owner-freebsd-net Mon Jan 1 21: 3: 9 2001 From owner-freebsd-net@FreeBSD.ORG Mon Jan 1 21:03:06 2001 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from tsunami.waterspout.com (tsunami.waterspout.com [208.13.56.11]) by hub.freebsd.org (Postfix) with ESMTP id 1FA0737B400 for ; Mon, 1 Jan 2001 21:03:06 -0800 (PST) Received: from waterspout.com (tsunami.fw.waterspout.com [208.13.60.34]) by tsunami.waterspout.com (8.9.3/8.9.3) with ESMTP id AAA58976; Tue, 2 Jan 2001 00:01:46 -0500 (EST) (envelope-from csg@waterspout.com) Message-Id: <200101020501.AAA58976@tsunami.waterspout.com> To: Julian Elischer Cc: "C. Stephen Gunn" , Garrett Wollman , Andrea Franceschini , Ferdinand Goldmann , "freebsd-net@FreeBSD.ORG" Subject: Re: Problems with VLAN and natd. In-Reply-To: Your message of "Sun, 31 Dec 2000 19:54:19 PST." <3A4FFF6B.F8C20C5@elischer.org> From: csg@waterspout.com (C. Stephen Gunn) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <99533.978412001.1@waterspout.com> Date: Tue, 02 Jan 2001 00:06:41 -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 31 Dec 2000 19:54:19 PST, Julian Elischer wrote: > > The current VLAN (and Ethernet) implementaiton in FreeBSD needs work. > > FreeBSD should should handle multiple ethernet encapsulations on > > the same physical interface, and relay packets to/from some subordinate > > interface. This support would factor-out the need for current > > work-arounds like if_vlan, and if_ef, and perhaps even if_tap. > > sounds like a perfect use for netgraph.. I've thought about this, and and a migation to netgraph would require significant changes to how FreeBSD handles Ethernet (and other IEEE 802) interfaces. For example, you would no longer simply ``ifconfig xl'', but associate a netgraph link-layer node on top of the xl interface, and a netgraph interface node on top of the link-layer node, which would function (mostly) like xl does now. Netgraph is an excellent technology. While your comment makes sense, there are several issues that will need to be addressed. For instance, the current ARP implementation in FreeBSD is entangled with the generic ethernet code. I'm afraid to even contemplate the POLA and backward compatability issues involved. If this discussion is non-casual, we should eventually migrate it over to -arch. - Steve -- C. Stephen Gunn URL: http://www.waterspout.com/ WaterSpout Communications, Inc. Email: csg@waterspout.com 427 North 6th Street Phone: +1 765.742.6628 Lafayette, IN 47901 Fax: +1 765.742.0646 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message