#147 no networking when running devel-20090121 as NT service

v0.8.x (devel)

Works fine when running from commandline:

> colinux-daemon @config.conf


> colinux-daemon --install-service coLinux @config.conf
> net start colinux

results in linux booting without eth.

Can you reproduce?


P.S. Also it hung as I was switching back and forth between console and service instances

C:\coLinux\devel-20090121>net stop colinux
The coLinux service is stopping........
The coLinux service could not be stopped.

But that was the first time it hanged. But it was also the first time I was switching back and forth much, to collect log info.


  • Arya

    Arya - 2009-01-30
    • labels: --> 599596
    • milestone: --> v0.8.x (devel)
  • Arya

    Arya - 2009-01-30
    • labels: 599596 -->
  • Nobody/Anonymous

    Please upload or paste your config.conf here.
    What is your host system? Windows XP with SP..., or Windows 2000?

  • Arya

    Arya - 2009-01-30

    Sorry about that. XP Pro SP2

    cofs0=c:\ cofs1=d:\ root=/dev/cobd0

    Again, networking works fine when I launch from commandline, no networking when I launch as service. I haven't checked whether cofs works or not when launching as a service...

  • Henry N.

    Henry N. - 2009-01-31

    Hello Arya,

    this is a problem of "udev" and different user accounts from start as service vs. command line start. coLinux stores the random created MACs inside the per User registry. So, you will have different MACs between the different starts. Ones use the Windows System account and the other the local User account. You will have different MAC for the network adapters between the different boot types.

    In the not working "run as service" you would see the networks as eth2 and eth3, I'm afraid.
    You can check this with this command on Linux:
    cat /proc/net/dev

    More about this "udev" problem can read here:

    To fix this, you have two options:
    A) Copy the working random MACs to the config to have the same all times.
    1. Run command line version
    2. copy the MAC you will find with "ifconfig" for eth0 and eth1
    3. paste these MACs to your config.conf after the eth0 and eth1, for example:
    Fill out the xx with your digits. Remember to set two commas on eth1 to skip the TAP-Name.
    4. Shutdown coLinux and run it as service

    B) Setup a self made MAC for both adapters
    1. Run coLinux
    2. Remove all lines from /etc/udev/rules.d/z25_persistent-net.rules inside your Ubuntu.
    3. Please add unique MAC number for each network in config.conf, for example
    Remember to set two commas on eth1 to skip the TAP-Name.
    A simple rule for self creating such MAC numbers: It should start with 02, and than follow ten random hex digits. The number you will use, should not exist in your network area near you.
    4. Shutdown coLinux and start it again (don't use "reboot")

    With next starts it should have networks in both starting variants all times.

    For the "service could not be stopped" have no idea. Please open a new bug report, if you have more details.

  • Arya

    Arya - 2009-01-31

    Thanks henryn, I used option A with great success.

  • Henry N.

    Henry N. - 2009-02-05

    Ok. It was a problem from configuration. Will close this bug now.

  • Henry N.

    Henry N. - 2009-02-05
    • labels: --> Configuration
    • status: open --> closed-wont-fix

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks