Click to See Complete Forum and Search --> : Network interfaces assignment problem


Perdido
04-24-2004, 11:20 AM
Hello all,

I have two network interfaces. They have the same names in all my previous kernels (eth0 and eth1). I am using Debian Sid.

But when I boot my computer with a new kernel (2.6.5) from a completely new .config file (I was not very happy with the oldest one) the interfaces assignment has changed and they are renamed eth1 and eth2. So, the interfaces configuration doesn't match and they don't work.

Could you help me?.

gehidore
04-24-2004, 12:43 PM
what distro.

and you dont have a eth* thats built into your motherboard do you?

mdwatts
04-24-2004, 01:11 PM
Originally posted by gehidore
what distro.


Debian Sid (as above) ??

Perdido... See if adding

alias eth0 <module>
alias eth1 <module>

to /etc/modules.conf and running

depmod -ae

fixes that. Not sure if it will, but might be worth a try.

gehidore
04-24-2004, 01:12 PM
sorry missed that.

bwkaz
04-24-2004, 01:50 PM
From http://www.linux.org.uk/~davej/docs/post-halloween-2.6.txt

- Users of boxes with >1 NIC may find that for eg, eth0 and eth1 refer to
the opposites of what they did in 2.4. This is a bug that will be fixed
before 2.6.0. One option (or management workaround) for this is to use
'nameif' to name Ethernet interfaces. There is a HOWTO for doing this at
<http://xenotime.net/linux/doc/network-interface-names.txt> Guess it didn't get completely fixed before 2.6.0, or something like that. See if the "nameif" program or that HOWTO helps you at all.

mdwatts
04-24-2004, 02:30 PM
Originally posted by bwkaz

[code]- Users of boxes with >1 NIC may find that for eg, eth0 and eth1 refer to the opposites of what they did in 2.4. This is a bug that will be fixed before 2.6.0.

Wouldn't that mean eth0 is now eth1 and eth1 is eth0? What about eth1/eth2? :confused:

I was hoping what I previously suggested would force the kernel to use eth0 and eth1 instead of 1 & 2.

Perdido
04-24-2004, 04:26 PM
Originally posted by mdwatts
Debian Sid (as above) ??

Perdido... See if adding

alias eth0 <module>
alias eth1 <module>

to /etc/modules.conf and running

depmod -ae

fixes that. Not sure if it will, but might be worth a try.

Could you help me to know the modules names?. I don't know how to do it. I'm just a newbie.

Thank you for your help.

leyb
04-24-2004, 05:17 PM
bash$ lsmod
This lists the modules running on your machine.

je_fro
04-24-2004, 06:05 PM
Maybe I'm missing something, but why not just make changes to /etc/network/interfaces ?

bwkaz
04-24-2004, 06:12 PM
Originally posted by mdwatts
Wouldn't that mean eth0 is now eth1 and eth1 is eth0? What about eth1/eth2? :confused: Oh, you're right, I didn't see that. :o

Well, nameif still might be helpful anyway. It moves you away from any dependence on ethN at all.

mdwatts
04-25-2004, 11:10 AM
Originally posted by je_fro
Maybe I'm missing something, but why not just make changes to /etc/network/interfaces ?

Cause we like doing everything the hard way. :)

Does Debian use /etc/network/interfaces as SuSE does not?