Date: Tue, 30 Dec 2014 11:00:15 -0800 From: "Chris H" <bsd-lists@bsdforge.com> To: freebsd-net@freebsd.org, Martin Birgmeier <la5lbtyi@aon.at> Subject: Re: Tying down network interfaces Message-ID: <e1211bbe6b84b97c94b55d770eb2af92@ultimatedns.net> In-Reply-To: <54A2E8B6.3070801@aon.at> References: <54A2E8B6.3070801@aon.at>
next in thread | previous in thread | raw e-mail | index | archive | help
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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e1211bbe6b84b97c94b55d770eb2af92>