From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 11 01:24:10 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA37916A401 for ; Tue, 11 Apr 2006 01:24:10 +0000 (UTC) (envelope-from joseph@randomnetworks.com) Received: from rhyll.com (rhyll.com [70.84.96.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 402FE43D75 for ; Tue, 11 Apr 2006 01:24:10 +0000 (GMT) (envelope-from joseph@randomnetworks.com) Received: from localhost (localhost [127.0.0.1]) by rhyll.com (Postfix) with ESMTP id BDE7D2E07F; Mon, 10 Apr 2006 18:24:09 -0700 (PDT) Received: from rhyll.com ([127.0.0.1]) by localhost (sm01.rhyll.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08287-08; Mon, 10 Apr 2006 18:24:08 -0700 (PDT) Received: from [192.168.1.102] (adsl-69-225-42-239.dsl.skt2ca.pacbell.net [69.225.42.239]) by rhyll.com (Postfix) with ESMTP id 14D9E2E036; Mon, 10 Apr 2006 18:24:08 -0700 (PDT) In-Reply-To: <443ACCB6.8080306@bitfreak.org> References: <20060409090757.GW80492@spc.org> <20060409.184825.99254285.imp@bsdimp.com> <20060410194746.GY80492@spc.org> <20060410.141042.25162164.imp@bsdimp.com> <443ACCB6.8080306@bitfreak.org> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <40B160C1-719B-4FCA-A192-75432F3738D5@randomnetworks.com> Content-Transfer-Encoding: 7bit From: Joseph Scott Date: Mon, 10 Apr 2006 18:24:12 -0700 To: Darren Pilgrim X-Mailer: Apple Mail (2.749.3) X-Virus-Scanned: amavisd-new at rhyll.com Cc: mwm-keyword-freebsdhackers.102a7e@mired.org, scottl@samsco.org, ceri@submonkey.net, hackers@FreeBSD.org Subject: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2006 01:24:10 -0000 On Apr 10, 2006, at 2:23 PM, Darren Pilgrim wrote: > I think at this point it's been pretty well established that: > > - Device naming and unit numbering is not stable enough to avoid > breakage across hardware changes. > - There is a need for generic and/or descriptive interface naming > independent of driver- and probe-order-based naming. > - There are static bits of information available about each device > in the system that can be used to locate a specific device that > would be sufficient to allow assignment of a network configuration > to a physical device, not it's attached name. > > If I were to write an rc.d script to use descriptive network > interface names and wire configs to static hardware identification, > would there be support for such a feature? Being mostly a lurker on this list I don't know that my vote would count for much, but yes I'd support such a feature. Thank you also for outlining the issues for this thread in a simple manner. -- Joseph Scott joseph@randomnetworks.com http://joseph.randomnetworks.com/