Cooperative Linux

Andrew Roth wrote:
> I've been playing around with different colinux versions and installed
> new virtual devices, and it seems with each one, linux added a new eth#
> device.  So now I'm at eth14.  Needless to say it's a bit annoying for
> my config files.  It seems to be storing these device numbers in the
> linux distribution somewhere, but I can't find where.  Does anyone know
> how I can clear out the old devices and start at eth0 again?

Follow http://www.colinux.org/snapshots/devel-RUNNING:

 -- Some dev distries increase eth1, eth2, eth3, ... on every boot.
    Typicaly have no network, but can see it with "cat /proc/net/dev".
    As workarrount set an unique MAC address for all network interfaces
    in config file. Or disable udev.
    Debian: Remove all entries from
/etc/udev/rules.d/z25_persistent-net.rules

-- 
Henry N.

Ah, thanks!

A few questions as I try to understand this.  Isn't the purpose of udev to
keep the devices the *same*?  It seems pretty bizarre to increase devices on
every boot -- that's a lot of new devices.  Ubuntu (which I'm using) doesn't
seem to add devices on boot, only on actually new tap devices (maybe this is
what you mean?).

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?

-Andrew

On Feb 19, 2008 8:09 PM, Henry Nestler <Henry.Ne@...> wrote:

> Andrew Roth wrote:
> > I've been playing around with different colinux versions and installed
> > new virtual devices, and it seems with each one, linux added a new eth#
> > device.  So now I'm at eth14.  Needless to say it's a bit annoying for
> > my config files.  It seems to be storing these device numbers in the
> > linux distribution somewhere, but I can't find where.  Does anyone know
> > how I can clear out the old devices and start at eth0 again?
>
> Follow http://www.colinux.org/snapshots/devel-RUNNING:
>
>  -- Some dev distries increase eth1, eth2, eth3, ... on every boot.
>    Typicaly have no network, but can see it with "cat /proc/net/dev".
>    As workarrount set an unique MAC address for all network interfaces
>    in config file. Or disable udev.
>    Debian: Remove all entries from
> /etc/udev/rules.d/z25_persistent-net.rules
>
> --
> Henry N.
>

>
> 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#.

-Andrew


> On Feb 19, 2008 8:09 PM, Henry Nestler <Henry.Ne@...> wrote:
>
> > Andrew Roth wrote:
> > > I've been playing around with different colinux versions and installed
> > > new virtual devices, and it seems with each one, linux added a new
> > eth#
> > > device.  So now I'm at eth14.  Needless to say it's a bit annoying for
> > > my config files.  It seems to be storing these device numbers in the
> > > linux distribution somewhere, but I can't find where.  Does anyone
> > know
> > > how I can clear out the old devices and start at eth0 again?
> >
> > Follow http://www.colinux.org/snapshots/devel-RUNNING:
> >
> >  -- Some dev distries increase eth1, eth2, eth3, ... on every boot.
> >    Typicaly have no network, but can see it with "cat /proc/net/dev".
> >    As workarrount set an unique MAC address for all network interfaces
> >    in config file. Or disable udev.
> >    Debian: Remove all entries from
> > /etc/udev/rules.d/z25_persistent-net.rules
> >
> > --
> > Henry N.
> >
>
>

andrewroth@... 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.

Rainer Zocholl wrote:
> andrewroth@... 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.