Could someone please point me to NON RedHat/Debian/... centric
tool to determine the proper ethernet for now ?
Modules are not an option for me here . Imo: If this can be done
with modules it should well be possible for staticly built
drivers as well . Tia , JimL
On Thu, 8 May 2003, Ray Lee wrote:
> Jean Tourrilhes wrote:
> > My belief is that configuration scripts should be specified in
> > term of MAC address (or subset) and not in term of device name. Just
> > like the Pcmcia scripts are doing it.
> Debian already supports this, integrated into the normal scheme for
> dealing with interfaces. Anyone running Debian can take a look at
> /usr/share/doc/ifupdown/examples directory, the network-interfaces.gz
> file contains sample /etc/network/interfaces stanzas for configuring
> your interfaces via MAC address:
> auto eth0 eth1
> mapping eth0 eth1
> script /path/to/get-mac-addr.sh
> map 11:22:33:44:55:66 lan
> map AA:BB:CC:DD:EE:FF internet
> iface lan inet static
> address 192.168.42.1
> netmask 255.255.255.0
> pre-up /usr/local/sbin/enable-masq $IFACE
> iface internet inet dhcp
> pre-up /usr/local/sbin/firewall $IFACE
> You can even do something like:
> iface wireless inet dhcp
> wireless_key 12345678901234567890123456
> A sample get-mac-address.sh is in the same directory, though it has a
> typo (missing a close paren -- I need to report that...). This same
> scheme works for pinging some well-known host to determine where you
> are, or using ARPs, or whatever. I use it on my laptop with PCMCIA
> cards, works great.
> Ray
-- +------------------------------------------------------------------+ | James W. Laferriere | System Techniques | Give me VMS | | Network Engineer | P.O. Box 854 | Give me Linux | | babydr@baby-dragons.com | Coudersport PA 16915 | only on AXP | +------------------------------------------------------------------+ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/