udev z25_persistent-net.rules problem
Hello,
New machine running the vmlinuz-2.6.18-6-amd64 kernel and 4 GB of ram.
I set up the /etc/network/interfaces file up as such:
--------------------------------------------------------------------------------
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 209.102.12x.xx
netmask 255.255.255.0
network 209.102.124.0
broadcast 209.102.124.255
gateway 209.102.12x.x
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 20x.129.4x.2x 20x.10x.12x.xx 20x.10x.12x.xx
dns-search pcez.com
(The numbers are changed to protect the innocent)
-----------------------------------------------------------------------------------
The /etc/udev/rules.d/z25_persistent-net.rules file looks like this the
first time you boot it up?
----------------------------------------------------------------------------------
# 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.
# MAC addresses must be written in lowercase.
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:98:68:74", NAME="eth0"
---------------------------------------------------------------------------------
The next time it boots up the machine does not recognize eth0
and there is a eth1 added to the above file. If I change the
/etc/network/interfaces file to eth1 and do a ifup -a there is the
Internet.
Each time the machine is booted up the number climbs eth1 eth2 eth3 ...
etc.
Below is the z25_persistent-net.rules after 11 reboots, and if you want
the ethernet to work you need to bump up the eth? in the interfaces file.
If you remove the z25_persistent-net.rules file when you reboot it will
set the ethernet to eth0.
Any ideas?
What I have done just so I can run the machine is to remove the
z25_persistent-net.rules file as part of the reboot process. This works.
Thanks,
Ken
-------------------------------------------------------------------
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:98:68:74",
NAME="eth0"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:26:35:2a",
NAME="eth1"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:a5:e5:e6",
NAME="eth2"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:71:d8:88",
NAME="eth3"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:f4:d0:22",
NAME="eth4"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:8e:b6:f5",
NAME="eth5"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:b8:bd:71",
NAME="eth6"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:26:5d:d1",
NAME="eth7"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:b5:3a:51",
NAME="eth8"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:a4:57:52",
NAME="eth9"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:02:f1:58",
NAME="eth10"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:be:90:42",
NAME="eth11"
Reply to: