[ previous ] [ next ] [ threads ]
 From:  Chris Buechler <cbuechler at gmail dot com>
 To:  m0n0wall-dev Mailing List <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall-dev] Making interface assignments more resilient
 Date:  Sun, 6 Nov 2005 20:07:47 -0500
On 11/6/05, Kris Maglione <bsdaemon at comcast dot net> wrote:
> Also, I'm planing to replace the prompt for interface name... most people
> would rather read "Intel 82559 Pro/100 Ethernet" than fxp0.

yeah, except if you go solely on driver, with the list of various
cards and manufacturers supported by many of the drivers, you could
easily have a half page list of what it might be.  :)

there are other options, like parsing dmesg might produce more
specific output under certain circumstances.  Even at that, you'll
typically end up with the chipset on the card, which under many
circumstances won't tell the user anything since it has no relation to
the vendor name on the card.  Looking through some of my oddball
NIC's, like a DLink card supported by the sis driver will come up as
something like "NatSemi DPxxxxx", a Linksys rl card as "Accton MPX
5030/5038", etc.  This remains as obscure as "sis" or "rl".