Option 1:
Use modules instead of kernel built in drivers. You can setup aliases,
something like
alias eth0 8139too
alias eth1 via-rhine
in /etc/modutils/aliases
Option 2:
Make a script that configure each interface using it MAC address, something
like
auto eth0 eth1
mapping eth0 eth1
script /path/to/get-mac-addr.sh
map 00:48:54:65:AA:AA internal
map 00:48:54:65:BB:BB external
iface internal inet static
address 192.168.0.
netmask 255.255.255.0
pre-up /path/to/internal-firewall.sh $IFACE
iface internet inet dhcp
pre-up /path/to/internet-firewall.sh $IFACE
in /etc/network/interfaces
Matias Lambert
OSInet Telecomunicaciones
Capital Federal - Buenos Aires
Argentina - CA1185ACA
http://www.osinet.com.ar
> -----Mensaje original-----
> De: Eric Sproul [mailto:[EMAIL PROTECTED]
> Enviado el: Jueves, 29 de Enero de 2004 05:47 p.m.
> Para: [EMAIL PROTECTED]
> Asunto: Re: 2.6 kernel network interface assignment order
>
>
> On Thu, 2004-01-29 at 14:55, Franz Georg Köhler wrote:
> > This occasionally happens with new kernel releases.
>
> I'd like to know why.
>
> > Swap your configuration...
>
> Again, I'd like to know *why* it happens rather than blindly changing
> configs. What if I had 3 interfaces, what would happen then? I
> wouldn't know which would end up where.
>
> Anyone have any more constructive advice?
> Eric
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
>
>
BEGIN:VCARD
VERSION:2.1
N:Lambert;Matias;German
FN:Matias Lambert ( OSInet )
ORG:OSInet TeleComunicaciones
TEL;WORK;VOICE:+54 11 4861 5616
TEL;HOME;VOICE:+54 11 4861 5616
TEL;CELL;VOICE:+54 11 (15) 4429 9469
TEL;WORK;FAX:+54 11 4861 5616
TEL;HOME;FAX:+54 11 4861 5616
ADR;WORK:;;Panamá 933 12 E;Capital Federal;Buenos Aires;C1185ACA;Argentina
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Panam=E1 933 12 E=0D=0ACapital Federal, Buenos Aires C1185ACA=0D=0AArgentina
URL;WORK:http://www.osinet.com.ar
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
REV:20030313T150013Z
END:VCARD
