mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ray Lee <ray-lk@madrabbit.org>
To: jt@bougret.hpl.hp.com, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: The magical mystical changing ethernet interface order
Date: 08 May 2003 16:38:09 -0700	[thread overview]
Message-ID: <1052437088.13561.36.camel@orca.madrabbit.org> (raw)

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


             reply	other threads:[~2003-05-08 23:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 23:38 Ray Lee [this message]
2003-05-09 12:41 ` Dick Streefland
2003-05-09 14:33 ` Mr. James W. Laferriere
  -- strict thread matches above, loose matches on Subject: below --
2003-05-10  7:42 Thomas Hood
2003-05-08 19:32 Jean Tourrilhes
2003-05-08 21:43 ` Eli Carter
2003-05-08 22:19   ` Jean Tourrilhes
2003-05-08 21:46 ` Alan Cox
2003-05-08 23:23   ` Randy.Dunlap
2003-05-07 13:14 Russell King
2003-05-07 15:18 ` Dick Streefland
2003-05-07 15:38   ` Jeff Garzik
2003-05-07 15:24 ` Randy.Dunlap
2003-05-07 17:14   ` Russell King
2003-05-07 22:04     ` Andrew Morton
2003-05-07 22:28       ` Dave Hansen
2003-05-08 12:05         ` David S. Miller
2003-05-08 14:55           ` Alan Cox
2003-05-08 14:54             ` David S. Miller
2003-05-08 16:24               ` Arnaldo Carvalho de Melo
2003-05-08 16:26               ` Jeff Garzik
2003-05-08 16:30                 ` Randy.Dunlap
2003-05-11 18:41                   ` Jeff Garzik
2003-05-08 17:56               ` Kai Germaschewski
2003-05-08 17:36           ` Linus Torvalds
2003-05-09  6:51           ` Richard Henderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1052437088.13561.36.camel@orca.madrabbit.org \
    --to=ray-lk@madrabbit.org \
    --cc=jt@bougret.hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome