From owner-freebsd-net@FreeBSD.ORG  Tue Dec 30 19:00:25 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 071EF858
 for <freebsd-net@freebsd.org>; Tue, 30 Dec 2014 19:00:25 +0000 (UTC)
Received: from udns.ultimatedns.net (unknown
 [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a])
 (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 D33833072
 for <freebsd-net@freebsd.org>; Tue, 30 Dec 2014 19:00:24 +0000 (UTC)
Received: from ultimatedns.net (localhost [127.0.0.1])
 by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id sBUJ0FZs035342;
 Tue, 30 Dec 2014 11:00:15 -0800 (PST)
 (envelope-from bsd-lists@bsdforge.com)
To: freebsd-net@freebsd.org, Martin Birgmeier <la5lbtyi@aon.at>
In-Reply-To: <54A2E8B6.3070801@aon.at>
References: <54A2E8B6.3070801@aon.at>
From: "Chris H" <bsd-lists@bsdforge.com>
Subject: Re: Tying down network interfaces
Date: Tue, 30 Dec 2014 11:00:15 -0800
Content-Type: text/plain; charset=UTF-8; format=fixed
MIME-Version: 1.0
Message-id: <e1211bbe6b84b97c94b55d770eb2af92@ultimatedns.net>
Content-Transfer-Encoding: 8bit
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 19:00:25 -0000

On Tue, 30 Dec 2014 19:02:30 +0100 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.
Just for starters, you might simply issue:
ifconfig
Which will dump the values of both NIC's (and other net related)
But once you've done that, you could issue a:
ifconfig sis0 down
then watch the blinking lights to help determine which NIC belongs
to which number. Not extremely elegant, but will at least help
narrow down which NIC, is which.
Then in the end, you can allocate your NIC's out of rc.conf(5).

--Chris

> 
> -- Martin
> 
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"