From owner-freebsd-chat Thu Sep 28 23:36:42 2000 Delivered-To: freebsd-chat@freebsd.org Received: from smtppop3.gte.net (smtppop3pub.gte.net [206.46.170.22]) by hub.freebsd.org (Postfix) with ESMTP id 91FB337B423 for ; Thu, 28 Sep 2000 23:36:39 -0700 (PDT) Received: from gte.net (evrtwa1-ar4-144-246.dsl.gtei.net [4.34.144.246]) by smtppop3.gte.net with ESMTP ; id BAA31221595 Fri, 29 Sep 2000 01:32:35 -0500 (CDT) Received: (from res03db2@localhost) by gte.net (8.9.3/8.9.3) id XAA01285; Thu, 28 Sep 2000 23:36:23 -0700 (PDT) (envelope-from res03db2@gte.net) Date: Thu, 28 Sep 2000 23:36:23 -0700 (PDT) From: Robert Clark Message-Id: <200009290636.XAA01285@gte.net> To: des@ofug.org, tlambert@primenet.com Subject: Re: Ideas about network interfaces. Cc: dot@dotat.at, freebsd-chat@FreeBSD.ORG, ragnar@sysabend.org, res03db2@gte.net In-Reply-To: <200009290033.RAA05430@usr05.primenet.com> Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Its funny to me that the idea I wanted to ask about, that I would've thought would be the least interesting to people, would be the one most talked about. My thought, is that we don't name our disk devices based on the brand of the scsi controller. Why do we specify an interface to talk to, based on a brand name. Is there any way to have more than one instance of the network stack running on one system? If we could run more than one instance of the network stack, we could give each a set of (ethernet) ports to work with. Would it make sens to give one port to a firewall package, and several ports to some other use. Or ultimately, one instance of the OS could have interfaces 1 2 and 3, and another instance of the OS could have interfaces 4 5 and 6. Without traffic leakinf from one instance of the OS to the other. Thanks, [RC] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message