From owner-freebsd-net@FreeBSD.ORG  Tue Dec 30 20:13:33 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 7FEBDD79
 for <freebsd-net@freebsd.org>; Tue, 30 Dec 2014 20:13:33 +0000 (UTC)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com
 [IPv6:2607:f8b0:4003:c06::232])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 41EC91CFD
 for <freebsd-net@freebsd.org>; Tue, 30 Dec 2014 20:13:33 +0000 (UTC)
Received: by mail-oi0-f50.google.com with SMTP id x69so33627941oia.9
 for <freebsd-net@freebsd.org>; Tue, 30 Dec 2014 12:13:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=Cz7++QHZCauhJwn/mqcf3sq8xlp8ewAUOVCDO2tkATI=;
 b=WEC89dOs3JIZtfxGqys06sU+fioT3MQhq4taYlzA62/9amU3qBGr0h5oc8GKIsFhZp
 QRIxCi/36bcHPQy0lsP4du7wmw80QT1nxGG9NRiiqW03JNM4h8ZAmZscvnfERrfTO82I
 Tggc6IrPt5qJyhQpyPkz0xNRB5Ga9MI0V/Up0pPEL3GY9OfIEubyIoOxOgxpBGk7ZT4t
 Y4y0JOzsinR4fI6R2uLRkfMflVGOGWcV5xADZVOtzUp4FvfpeBmrMDWxIQrNo7g9nH43
 Y798CXxSRKs00lWKd7JjdrY7hOCWkSqsFGEO9myZLCznr6OI77wLyamPjmD0KjZ6QsDl
 yLlw==
MIME-Version: 1.0
X-Received: by 10.202.185.69 with SMTP id j66mr35339965oif.86.1419970412707;
 Tue, 30 Dec 2014 12:13:32 -0800 (PST)
Received: by 10.202.76.208 with HTTP; Tue, 30 Dec 2014 12:13:32 -0800 (PST)
Received: by 10.202.76.208 with HTTP; Tue, 30 Dec 2014 12:13:32 -0800 (PST)
In-Reply-To: <54A2E8B6.3070801@aon.at>
References: <54A2E8B6.3070801@aon.at>
Date: Tue, 30 Dec 2014 12:13:32 -0800
Message-ID: <CAOjFWZ5OmuBKSeFAaxw0x-zPY8E9azf7SSU5+5OvaLZhXdoJBg@mail.gmail.com>
Subject: Re: Tying down network interfaces
From: Freddie Cash <fjwcash@gmail.com>
To: Martin Birgmeier <la5lbtyi@aon.at>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
Cc: freebsd-net <freebsd-net@freebsd.org>
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 20:13:33 -0000

On Dec 30, 2014 10:02 AM, "Martin Birgmeier" <la5lbtyi@aon.at> wrote:
>
> 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.

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