From: Andrew R. <and...@gm...> - 2008-02-20 03:24: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#. -Andrew > On Feb 19, 2008 8:09 PM, Henry Nestler <Hen...@ar...> 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. > > > > |