Re: [coLinux-users] Problem with windows service and ndis-bridge

[Lars G. <Lar...@re...>]

Hi Henry,

thanks for the support, my problem was depending on the MAC address (thanks again for the good explanation). 

For others in this situation: I had to deinstall the service (--remove-service)  and install it again before it works (I guess this was probably my registry manipulation).

Cheers
Lars 
PS: Just for information, "tap0" is correct, I have renamed my network cards in windows: eth0=LAN, tap0=TAP-Win32 and bri0= Windows Bridge.

-----Ursprüngliche Nachricht-----
Von: Henry Nestler [mailto:hen...@ar...] 
Gesendet: Dienstag, 3. August 2010 22:05
An: Lars Grundei
Cc: 'col...@li...'
Betreff: Re: [coLinux-users] Problem with windows service and ndis-bridge

  Hello Lars,

On 03.08.2010 15:43, Lars Grundei wrote:
> I use colinux 0.78 with the native windows network bridge, it runs fine if I start it from a console.
> My problem is it to get up the windows service with network support. I can install, start and attach a console to the service.
> But it is not possible for me, to start the bridged interface (eth2), ifup eth2 prints this:
> -----------------------------
> SIOCSIFADDR: No such device
> eth2: ERROR while getting interface flags: No such device
> SIOCSIFNETMASK: No such device
> eth2: ERROR while getting interface flags: No such device
> Failed to bring up eth2.
> -----------------------------
>
> In the wiki, I've read something about service dependencies, but this sections seems to e outdated for 0.78 and also does not affect brigdeg network. However I have tried to add Bridge and some other to the service dependencies, without success.
>
> Service Dependicies:
> --------------------
> CoLinuxDriver
> Bridge
> BridgeMP
> NPF
> tap0801co
Dependicies tap0801co (TAP-Win32), NPF (PCAP-bridge) you not need, if you not use such network options. They will automatically set, by the colinux-daemon, if they would be configured in your config.

Please don't set Bridge and BridgeMP. CoLinux says ndis-bridge, because it works as a bridge. But it's not using any bridge drivers from Windows.

And last: "Service Dependicies" means only, that this driver must be started before coLinux can start. So it is more for delayed coLinux start on the Windows boot, not for the manually start.


> PS: Extract from the config file:
> -----------------------------
> # Slirp for internet connection (outgoing)
> #eth0=slirp
>
> # Tuntap as private network between guest and host on second linux device
> #eth1=tuntap
>
> # brigded networks
> eth2=ndis-bridge,"tap0"
> -----------------------------

I think, "tap0" is not right there. Or your real network is an openVPN 
tunnel?

Running from command line and as service, will use different Windows 
user accounts. With different user accounts, you would have different 
"automatic"-MAC for the eth2. DIfferent MAC your udev inside Linux will 
rename eth2 to any other eth3, eth3 or what ever.

To solve this, please set a unic MAC for the eth2 in the coLinux config.
Please read answer #4 in Forum at 
http://sourceforge.net/projects/colinux/forums/forum/342354/topic/3768555

Or for udev renaming problem please read:
http://colinux.wikia.com/wiki/Wubi#udev:_renamed_network_interface_eth0_to_eth2

-- 
Henry N.