Menu
▾
▴
Re: [Devil-linux-develop] Potential bug - save-config includes "/etc/udev/rules.d/70-persistent-net.rules"
|
From: Bruce S. <bw...@re...> - 2010-04-20 16:11:46
|
My concern is if the computer has multiple NIC's of the same make/model and the interface numbers are dynamically assigned every time the computer is booted, it may not assign the same NIC to the same interface every time. It would probably assign them the same as long as nothing changes. But what if someone adds another piece of unrelated hardware that causes IRQ's to be reassigned? Or what if we upgrade DL to new kernel patches or new versions of other network software? I see a real possibility of the NIC/interface assignment changing upon boot. And now your firewall has reversed NIC's, potentially allowing the Internet full access to your private network. - BS On Tue, Apr 20, 2010 at 11:00, Steve Ralph <Ste...@sa...> wrote: > Hi there, > > I have been working to port some internal configuration scripts to > DL-1.4-RC3/486 and have installed to a USB key. This allows me to boot from > multiple different machines and continue work where I left off. > > When I boot from the original install and list the network interfaces > (either ifconfig or ip addr show), all seems OK. Once I run save-config, and > then boot from different hardware, I have an issue around the assignment of > the interface names. > > After some investigation, this seems to be because the file > "/etc/udev/rules.d/70-persistent-net.rules " is included in the tarball > created by save-config. This file links the mac-address to the device name > (eg, 00:08:02:01:02:03 is named eth0). > > When this file already exists (eg, after save-config has been run), and the > usb-key boots on different hardware, udev says eth0 is already assigned > because the mac address of the previous machine is linked to eth0 in > 70-persistent-net.rules (even if the listed mac-address is nowhere to be > seen on this hardware), and assigns the new mac-address to the next > available device, eg, eth1. > > If I save-config again the problem is exacerbated! On the second and > subsequent hardware, interfaces are assigned after the devices allocated in > 70-persistent-net.rules, but any statically configured addresses are > assigned to the original network devices. > > EG: > 1st machine > IF=eth0 MAC=00:08:02:01:02:03 IP=10.1.1.1/24 > IF=eth1 MAC=00:08:02:01:02:04 IP=10.1.2.1/24 > IF=eth2 MAC=00:08:02:01:02:05 IP=10.1.3.1/24 > > 2nd machine > IF=eth0 MAC=00:08:02:01:02:06 > IF=eth1 MAC=00:08:02:01:02:07 > IF=eth2 MAC=00:08:02:01:02:08 > > When using the saved-config from the first machine on the second > machine > IF=eth0 MAC=00:08:02:01:02:03 IP=10.1.1.1/24 Interface > Not available as MAC address not found! > IF=eth1 MAC=00:08:02:01:02:04 IP=10.1.2.1/24 Interface > Not available as MAC address not found! > IF=eth2 MAC=00:08:02:01:02:05 IP=10.1.3.1/24 Interface > Not available as MAC address not found! > IF=eth3 MAC=00:08:02:01:02:06 IP=Unassigned Interface > available as MAC address found but NO IP Address assigned > IF=eth4 MAC=00:08:02:01:02:07 IP=Unassigned Interface > available as MAC address found but NO IP Address assigned > IF=eth5 MAC=00:08:02:01:02:08 IP=Unassigned Interface > available as MAC address found but NO IP Address assigned > > This issue could also occur if a pre-saved config file was installed on new > kit as part of a hardware only upgrade. > > I suggest a fix would be to exclude the file > "/etc/udev/rules.d/70-persistent-net.rules" from the tar created with > save-config allowing this file to be dynamically created at boot up like on > the initial boot. > > Before I log a call on mantis I would appreciate a sanity check first, to > confirm that I haven't missed anything obvious. > > Additionally, although I have had no issues with the CD assignment, should > "/etc/udev/rules.d/70-persistent-cd.rules" file also be excluded from the > save-config? > > Regards - Steve. |