Re: Two identical usb networking cards problem

On Sat, Mar 03, 2007 at 02:19:20PM +0100, David Fokkema wrote:
Hi group,

Hi,

I installed debian etch on an NSLU2. It has an internal network card
which is brought up automatically at boot time. I have two additional
usb network cards attached to a hub which are identical. Only one of
them is brought up at boot time. Which one, that is (well, seems to be,
anyway) completely random, :-/

My /etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
address 192.168.20.10
netmask 255.255.255.0

allow-hotplug eth1
iface eth1 inet static
address 192.168.31.10
netmask 255.255.255.0

allow-hotplug eth2
iface eth2 inet dhcp
pre-up ethtool -s eth2 autoneg off speed 10


If I change the allow-hotplug to auto, my problem is solved.

My question: how can I find out which daemon/script is bringing up my
two out of three interfaces and how can I make sure it brings up all
three (without resorting to auto lines, apparently allow-hotplug
should
work).



Take a look here :

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=403706

The following commands are your friends :
# ip link
or
# ifconfig -a

If you can see an interface names as ethX_rename or something like that,
it means udev mess it up. You can fix it, by writing udev rules. This is
the way I do to ensure my interfaces get the right name.

By the way, you can see the name supply by udev :

<<<<<<<<<<<
sid:/var/lib# cat /etc/udev/rules.d/z25_persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules
# file.
#
# You can modify it, as long as you keep each rule on a single line.

# Firewire device 0011d80000b05f6c (ohci1394)
SUBSYSTEM=="net", DRIVERS=="?*",
ATTRS{address}=="00:11:d8:00:00:b0:5f:6c", NAME="eth0"

# PCI device 0x10de:0x0373 (forcedeth)
#SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:17:31:a4:0b:4e",
NAME="eth1"

# PCI device 0x10de:0x0373 (forcedeth)
#SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:17:31:a3:ff:31",
NAME="eth2"

# PCI device 0x1113:0x1211 (8139too)
#SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:10:b5:e1:5c:e5",
NAME="eth3"

# PCI device 0x10ec:0x8139 (8139too)
#SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:08:a1:96:82:35",
NAME="eth4"
<<<<<<<<<

Hope it helps.

--
Franck Joncourt
http://www.debian.org
http://smhteam.info/wiki/
GPG server : pgpkeys.mit.edu
Fingerprint : C10E D1D0 EF70 0A2A CACF 9A3C C490 534E 75C0 89FE

Attachment: signature.asc
Description: Digital signature

Relevant Pages

  • Intel Pro network
    ... Network Connection ... iface eth0 inet dhcp ... iface eth2-mohan inet dhcp ...
    (Debian-User)
  • Re: Need a little help with my network configuration
    ... Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 ... # This file describes the network interfaces available on your system ... iface lo inet loopback ...
    (Debian-User)
  • Re: Need a little help with my network configuration
    ... Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 ... # This file describes the network interfaces available on your system ... iface lo inet loopback ...
    (Debian-User)
  • Re: Default Route On Boot.
    ... your gateway and your address are on the same network. ... >there are three ways to set a default route when the machine boots. ... >iface eth0 inet static ...
    (Debian-User)
  • Re: Devd event from GEOM?
    ... >> to a network interface, as kqueue requires a file descriptor. ... > I's suspect that da0 would arrive in GEOM before newbus. ... Part of the attachment is to add it to GEOM. ...
    (freebsd-current)