From owner-freebsd-net@FreeBSD.ORG Wed Dec 31 10:03:41 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3A8DEF15 for ; Wed, 31 Dec 2014 10:03:41 +0000 (UTC) Received: from email.aon.at (smtpout02.highway.telekom.at [195.3.96.113]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7B5FD67255 for ; Wed, 31 Dec 2014 10:03:39 +0000 (UTC) Received: (qmail 16868 invoked from network); 31 Dec 2014 10:03:35 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on WARSBL607.highway.telekom.at X-Spam-Level: Received: from 91-113-62-244.adsl.highway.telekom.at (HELO gandalf.xyzzy) ([91.113.62.244]) (envelope-sender ) by smarthub83.res.a1.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP; 31 Dec 2014 10:03:35 -0000 X-A1Mail-Track-Id: 1420020215:16842:smarthub83:91.113.62.244:1 Received: from mizar.xyzzy (mizar.xyzzy [192.168.1.19]) by gandalf.xyzzy (8.14.9/8.14.9) with ESMTP id sBVA3YbH004978; Wed, 31 Dec 2014 11:03:35 +0100 (CET) (envelope-from la5lbtyi@aon.at) Message-ID: <54A3C9F6.6000603@aon.at> Date: Wed, 31 Dec 2014 11:03:34 +0100 From: Martin Birgmeier Organization: MBi at home User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Freddie Cash Subject: Re: Tying down network interfaces References: <54A2E8B6.3070801@aon.at> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Dec 2014 10:03:41 -0000 The devices are PCI cards, no USB is involved. I assume that I'd have to add lines similar to hint.sis.0.at="pci0:9:0" to /boot/device.hints, but I am unsure of the correct syntax. See also these old articles (which ultimately seem to have gone unanswered): http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190453.html , http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190624.html -- Martin On 12/30/14 21:13, Freddie Cash wrote: > > On Dec 30, 2014 10:02 AM, "Martin Birgmeier" > wrote: > > > > Hi, > > > > I have two network interfaces as follows: > > > > sis0: port 0xa400-0xa4ff mem > > 0xd5800000-0xd5800fff irq 9 at device 9.0 on pci0 > > sis1: port 0x9400-0x94ff mem > > 0xd4800000-0xd4800fff irq 11 at device 12.0 on pci0 > > > > When sis0 breaks down, sis1 gets renumbered as sis0, wreaking havoc > > (mostly on my brains until I figure out which card is actually > affected). > > > > How do I tie down these two interfaces so that they always stay as sis0 > > and sis1, respectively, regardless of which ones are present in the > > system? - I expect to insert something into /boot/device.hints. > > There was a recent thread on one of the lists about using devd to name > USB Ethernet devices based on their MAC or serial number. Something > like that should be useful for naming NICs something constant. > > There's also a bug report for it with a working solution. > > Cheers, > Freddie >