From owner-freebsd-net@FreeBSD.ORG  Tue Dec 30 18:02:51 2014
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 6AF6D292
 for <freebsd-net@freebsd.org>; Tue, 30 Dec 2014 18:02:51 +0000 (UTC)
Received: from email.aon.at (nat-warsl417-01.aon.at [195.3.96.119])
 (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 BBF8F837
 for <freebsd-net@freebsd.org>; Tue, 30 Dec 2014 18:02:49 +0000 (UTC)
Received: (qmail 4728 invoked from network); 30 Dec 2014 18:02:41 -0000
Received: from unknown (HELO email.aon.at) ([172.18.1.205])
 (envelope-sender <la5lbtyi@aon.at>)
 by fallback43.highway.telekom.at (qmail-ldap-1.03) with SMTP
 for <freebsd-net@freebsd.org>; 30 Dec 2014 18:02:41 -0000
Received: (qmail 3760 invoked from network); 30 Dec 2014 18:02:32 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
 WARSBL604.highway.telekom.at
X-Spam-Level: 
Received: from 194-166-23-182.adsl.highway.telekom.at (HELO gandalf.xyzzy)
 ([194.166.23.182]) (envelope-sender <la5lbtyi@aon.at>)
 by smarthub77.res.a1.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP
 for <freebsd-net@freebsd.org>; 30 Dec 2014 18:02:32 -0000
X-A1Mail-Track-Id: 1419962552:3734:smarthub77:194.166.23.182:1
Received: from mizar.xyzzy (mizar.xyzzy [192.168.1.19])
 by gandalf.xyzzy (8.14.9/8.14.9) with ESMTP id sBUI2U0K003049
 for <freebsd-net@freebsd.org>; Tue, 30 Dec 2014 19:02:32 +0100 (CET)
 (envelope-from la5lbtyi@aon.at)
Message-ID: <54A2E8B6.3070801@aon.at>
Date: Tue, 30 Dec 2014 19:02:30 +0100
From: Martin Birgmeier <la5lbtyi@aon.at>
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: freebsd-net@freebsd.org
Subject: Tying down network interfaces
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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, 30 Dec 2014 18:02:51 -0000

Hi,

I have two network interfaces as follows:

sis0: <NatSemi DP8381[56] 10/100BaseTX> port 0xa400-0xa4ff mem
0xd5800000-0xd5800fff irq 9 at device 9.0 on pci0
sis1: <NatSemi DP8381[56] 10/100BaseTX> 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.

-- Martin