{"id":34,"date":"2007-11-15T20:17:09","date_gmt":"2007-11-16T03:17:09","guid":{"rendered":"http:\/\/www.kernelcrash.com\/blog\/2007\/11\/15\/cloning-linux-and-the-missing-eth0\/"},"modified":"2007-11-15T20:17:09","modified_gmt":"2007-11-16T03:17:09","slug":"cloning-linux-and-the-missing-eth0","status":"publish","type":"post","link":"https:\/\/www.kernelcrash.com\/blog\/cloning-linux-and-the-missing-eth0\/2007\/11\/15\/","title":{"rendered":"cloning linux and the missing eth0"},"content":{"rendered":"<p>To save some time today, I made a clone copy of an existing Slackware 12.0 installation. I basically booted the Slackware 12.0 host from a Slackware install CD and then did a tar to tar copy to an external USB drive. It all went pretty well. I set up lilo on the new disk and put the disk into the other machine (with an identical hardware spec) and booted it up.<\/p>\n<p>It booted up OK, but I noticed eth0 was missing. I did a &#8216;dmesg|grep eth&#8217; and sure enough it had found the e1000 network interface on this machine and configured it as eth0. However if I did a &#8216;ifconfig eth0 1.2.3.4&#8217;, I got:<\/p>\n<p><code>SIOCSIFADDR: No such device<br \/>\neth0: ERROR while getting interface flags: No such device<\/code><\/p>\n<p>Hmmm, very odd. Eventually I did a &#8216;ifconfig eth2 1.2.3.4&#8217; and that worked. In this case eth2 was the e1000 network interface on this machine. dmesg did not seem to mention anything about eth2. It only mentioned eth0.<\/p>\n<p>Eventually, I found <a href=\"http:\/\/www.virtualbox.org\/ticket\/660\">this post<\/a> about cloning a virtual machine. Basically it&#8217;s all to do this newish udev stuff on most recent linux distro&#8217;s. There&#8217;s some rule under \/etc\/udev\/rules.d that caches the MAC address of the eth0 interface. On Slackware the file is 75-network-devices.rules. Basically there is a line in that file that says that eth0 has a MAC address of aa:bb:cc:dd:ee:ff. On my new machine, the MAC address is obviously different, so it moves eth0 to the next free interface eth2 (on the old machine eth1 was a wifi card).<\/p>\n<p>So to fix this I just edited \/etc\/udev\/rules.d\/75-network-devices.rules, removed the the two old lines relating to eth0 and eth1, and modified the line containing my new MAC address to make sure it says &#8216;eth0&#8217;. Reboot and it&#8217;s all fixed.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>To save some time today, I made a clone copy of an existing Slackware 12.0 installation. I basically booted the Slackware 12.0 host from a Slackware install CD and then did a tar to tar copy to an external USB drive. It all went pretty well. I set up lilo on the new disk and [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-34","post","type-post","status-publish","format-standard","hentry","category-linux"],"_links":{"self":[{"href":"https:\/\/www.kernelcrash.com\/blog\/wp-json\/wp\/v2\/posts\/34","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kernelcrash.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kernelcrash.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kernelcrash.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kernelcrash.com\/blog\/wp-json\/wp\/v2\/comments?post=34"}],"version-history":[{"count":0,"href":"https:\/\/www.kernelcrash.com\/blog\/wp-json\/wp\/v2\/posts\/34\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.kernelcrash.com\/blog\/wp-json\/wp\/v2\/media?parent=34"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kernelcrash.com\/blog\/wp-json\/wp\/v2\/categories?post=34"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kernelcrash.com\/blog\/wp-json\/wp\/v2\/tags?post=34"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}