Re: [coLinux-users] getting rid of old ethernet devices

[Henry N. <Hen...@Ar...>]

Rainer Zocholl wrote:
> and...@gm...(Andrew Roth)  19.02.08 22:24
> 
>>> I'm also a bit confused by the workaround of adding a new mac
>>> address per device.  I thought you would want to force each new tap
>>> device to use the same mac address, to trick linux into thinking
>>> they're new devices?
>>>
> 
>> I figured this out now.  I was quite confused.  I see now you want
>> each device to have a unique, but consistent mac address, to make
>> linux recognize them on each boot.  When you don't specify a mac
>> address in the colinux conf, it assigns one at random, and udev then
>> thinks they're new devices and assigns them a new eth#.
> 
> Pay attention to which MAC Addresse you choose!
> There ist one reserved bit with must be "0"!
> 
> Once Suggestion for a MAC Start value was given:
> 
> 0A:C0:11:__:__:__
> 0A:C0:71:__:__:__
> 
> AC071 = "A COLI"nux in "hex modified l33t"(tm)
> 
> See thread 
> "No network anmore?"
> "colinux-Bugs-1861876 20071203-Snapshot -- ifconfig reports no networking"
> for more.

http://sourceforge.net/tracker/index.php?func=detail&aid=1861876&group_id=98788&atid=622063

coLinux version 0.8.0 saves random created MAC in Windows registry. This
should solve the problems for udev systems. The MAC will create random
only on first new device. "Used keys in Windows Registry" finds in end
of file colinux-daemon.txt.

To check the workarround, run the daemon in verbose mode
 "colinux-daemon -v 3 kernel=..."
This is an example with two networks (slirp and tuntap):
   kernel boot parameters: 'root=/dev/cobd0'
   eth0: MAC found in registry: 00:ff:e9:58:e0:00
   eth1: MAC found in registry: 00:ff:15:ae:00:00
   PID: 416
   ...

The MAC will save in registry in builds after 2008-01-12, here is the
changelog:
http://colinux.svn.sourceforge.net/viewvc/colinux?view=rev&revision=838

If you runs an older version with PCI and without this workarround, the
random MACs are not saved on Windows side, but udev has it in the
z25_persistent-net.rules. For that case needs to fix the file
z25_persistent-net.rules ones after you booted a coLinux with this
workarround.

Versions 0.7.2 without PCI support have not such problems.

-- 
Henry N.