On Wed, Jun 13, 2007 at 02:05:34AM +0200, Marco d'Itri wrote:
> On May 06, [EMAIL PROTECTED] wrote:
> > This machine has two ethernet interfaces, formerly eth0 and eth1, that
> > are used to form the bond0 interface. Upon upgrading from sarge to
> > etch, eth1 became eth2 which broke the bonding configuration. Here's
> I can't see how this could happen, if persistent-net.rules contained a
> rule for eth1.
Udev wasn't in use before the upgrade to etch, if that's what you mean,
so the entire configuration was created during the upgrade.
> > what's in /etc/udev/rules.d/z25_persistent-net.rules
> >
> > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:15:17:1a:69:d0",
> > NAME="eth0"
> >
> > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:15:17:1a:69:d0",
> > NAME="eth1"
>
> Did you manually create these rules? They lack the usual comment.
No, I didn't touch anything in /etc/udev.
> > I'm guessing what happened is it saw the bond0 interface, which has the
> > same MAC address as eth0, and generated an eth1 configuration for it
> > instead of bond0, thereby kicking eth1 up to eth2. In any case the
> Please report the output of:
>
> udevinfo -a -p /class/net/eth0/
> udevinfo -a -p /class/net/eth1/
> udevinfo -a -p /class/net/bond0/
$ udevinfo -a -p /class/net/eth0/
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/class/net/eth0':
KERNEL=="eth0"
SUBSYSTEM=="net"
DRIVER==""
ATTR{weight}=="0"
ATTR{tx_queue_len}=="1000"
ATTR{flags}=="0x1803"
ATTR{mtu}=="1500"
ATTR{operstate}=="up"
ATTR{dormant}=="0"
ATTR{carrier}=="1"
ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
ATTR{address}=="00:15:17:1a:69:d0"
ATTR{link_mode}=="0"
ATTR{type}=="1"
ATTR{features}=="0x1113a9"
ATTR{ifindex}=="1"
ATTR{iflink}=="1"
ATTR{addr_len}=="6"
looking at parent device
'/devices/pci0000:00/0000:00:02.0/0000:01:00.0/0000:02:02.0/0000:04:00.0':
KERNELS=="0000:04:00.0"
SUBSYSTEMS=="pci"
DRIVERS=="e1000"
ATTRS{msi_bus}==""
ATTRS{broken_parity_status}=="0"
ATTRS{modalias}=="pci:v00008086d00001096sv00008086sd00003476bc02sc00i00"
ATTRS{local_cpus}=="ff"
ATTRS{irq}=="501"
ATTRS{class}=="0x020000"
ATTRS{subsystem_device}=="0x3476"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{device}=="0x1096"
ATTRS{vendor}=="0x8086"
looking at parent device
'/devices/pci0000:00/0000:00:02.0/0000:01:00.0/0000:02:02.0':
KERNELS=="0000:02:02.0"
SUBSYSTEMS=="pci"
DRIVERS=="pcieport-driver"
ATTRS{msi_bus}=="1"
ATTRS{broken_parity_status}=="0"
ATTRS{modalias}=="pci:v00008086d00003518sv00000000sd00000000bc06sc04i00"
ATTRS{local_cpus}=="ff"
ATTRS{irq}=="503"
ATTRS{class}=="0x060400"
ATTRS{subsystem_device}=="0x0000"
ATTRS{subsystem_vendor}=="0x0000"
ATTRS{device}=="0x3518"
ATTRS{vendor}=="0x8086"
looking at parent device '/devices/pci0000:00/0000:00:02.0/0000:01:00.0':
KERNELS=="0000:01:00.0"
SUBSYSTEMS=="pci"
DRIVERS=="pcieport-driver"
ATTRS{msi_bus}=="1"
ATTRS{broken_parity_status}=="0"
ATTRS{modalias}=="pci:v00008086d00003500sv00000000sd00000000bc06sc04i00"
ATTRS{local_cpus}=="ff"
ATTRS{irq}=="16"
ATTRS{class}=="0x060400"
ATTRS{subsystem_device}=="0x0000"
ATTRS{subsystem_vendor}=="0x0000"
ATTRS{device}=="0x3500"
ATTRS{vendor}=="0x8086"
looking at parent device '/devices/pci0000:00/0000:00:02.0':
KERNELS=="0000:00:02.0"
SUBSYSTEMS=="pci"
DRIVERS=="pcieport-driver"
ATTRS{msi_bus}=="1"
ATTRS{broken_parity_status}=="0"
ATTRS{modalias}=="pci:v00008086d000025F7sv00000000sd00000000bc06sc04i00"
ATTRS{local_cpus}=="ff"
ATTRS{irq}=="511"
ATTRS{class}=="0x060400"
ATTRS{subsystem_device}=="0x0000"
ATTRS{subsystem_vendor}=="0x0000"
ATTRS{device}=="0x25f7"
ATTRS{vendor}=="0x8086"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
$ udevinfo -a -p /class/net/eth1/
device not found
zsh: exit 4 udevinfo -a -p /class/net/eth1/
$ udevinfo -a -p /class/net/bond0/
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/class/net/bond0':
KERNEL=="bond0"
SUBSYSTEM=="net"
DRIVER==""
ATTR{weight}=="0"
ATTR{tx_queue_len}=="0"
ATTR{flags}=="0x1403"
ATTR{mtu}=="1500"
ATTR{operstate}=="up"
ATTR{dormant}=="0"
ATTR{carrier}=="1"
ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
ATTR{address}=="00:15:17:1a:69:d0"
ATTR{link_mode}=="0"
ATTR{type}=="1"
ATTR{features}=="0x11389"
ATTR{ifindex}=="3"
ATTR{iflink}=="3"
ATTR{addr_len}=="6"
-ryan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
