colinux-users — coLinux users mailing list

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Mike M. <mme...@na...>]

On 8/5/2010 4:49 PM, Henry Nestler wrote:
>  On 05.08.2010 21:00, Mike Mestnik wrote:
>> On 8/5/2010 2:27 PM, Henry Nestler wrote:
>>>
>>>> However!!! Networking still is not functional.
>>>> Is there any debugging I can do?
>>> Use -v 3 as option for colinux-daemon, run it on command line (not as
>>> service) and read successfull all messages from network daemon.
>>>
>>> For more debugging disable eth0 under Linux ("ifconfig eth0 down) and
>>> watch, that the ping goes truely over eth1. On Windows site you can
>>> use Wireshark for watching the packets on TAP-Win32 adapter.
>>>
>>> You are using IP address with 169.254, I assume you have not set an IP
>>> address on windows side of TAP. So, you must wait very long time after
>>> start, before the device is ready. A better alternate would be to set
>>> a fixed IP address for the TAP on both ends (Linux  and Windows).
>>>
>>> Check the IP adress on both sides and verify, that the address masked
>>> with netmask matched the same network on both sides. Typicalle you
>>> must use the same netmask on both sides and the starting numbers
>>> should be the same (169.254.x.x) for both ends.
>>>
>> I'll try some of these, thank you.
>> ...What would I do if every thing works file when running as an 
>> application?
>
> Add a MAC in coLinux config, than running from command line and as 
> service are identical fro the network issue.
I got that logically these SHOULD be identical.  The truth seems as 
thought these are vary different.  Firstly you asked to run as an 
application and not as a service, so things sound different and look 
different.  Then there is the huge difference from being a service VS 
being an application, this surely will interject differences.  Finally 
the parameters passed are different, meaning logically these are 
different as different code paths are used.

Thus testing as a service is a far cry from testing as an application, 
especially when you already are dealing with something that DOESN'T.  
DOESN'T i.m.h.o. usually outweighs any SHOULD CAN MAY or WILL.

> If you leave blank the MAC, then coLinux use a random MAC, and this 
> number is different between the running from command line and running 
> as service.
>
> Next step would be to use "colinux-daemon --install-service ..." and 
> run it. You will have no differences.
> Of curse the image files you have created should be writable for the 
> Windows account "Service".
>
Great, there is a method of testing...  Though it removes a variable I 
don't feel it will always satisfy the issue here.

...You should make debugging while running as a service as easy as 
debugging while running as an application.
>
>>>> eth0=ndis-bridge
>>>> eth1=tuntap,,00:18:8B:26:44:88
>>> Without MAC and without name of your real ethernet card you would have
>>> two problems.
>> The MAC should be that of the emulated card... correct?  Having this
>> match the physical device would sound like ruin.
>
> Yes, the MAC is for the guest - the Linux side.
> And, to never matching a real adapter it should start with 02, not 
> with 00.
>
>>> 1. On startup the ndis-bride can attach to the TAP-Win32. That is a
>>> loopback to coLinux self. To solve this, you should add the name of
>>> real Ethernet card.
>> Please add code to prevent this, only bind to a TAP-Win32 device if it's
>> the only device or if it was specified by name.
>
> This is not possible. The rule for empty name is: Using the first 
> adapter, that has a link connection. 
I don't see this at all.  If you can choose the first connection based 
on weather it has or has-not link you can choose not to choose a 
connection based on it's other qualities, like the name of it's driver.
> The ndis does not know what network card is your choice. The 
> ndis-daemon is a separate daemon, that does not know some about the other
If you don't know then do nothing, perhaps a bug in ndis.  I see this, 
but it should avoid potentially broken configs.
> coLinux network daemons. You can have WLAN cards, cable cards, VPN 
> (also TAP-Win32).
> If ndis should not use the first that it will find, then set a name 
> into the config.
>
Better this read "If you have to use a VPN connection you must set a 
name into the config.  However for most users it's safe to leave this 
blank."

Currently it's vary unsafe to leave it blank and the docs don't point 
out that it's mandatory.  So if you can't fix this bug then make the 
name required and die if it's not set.

> Other case you can sort the network order under Windows, so the 
> TAP-Win32 is not the first. This is of curse nothing for your installer.
>
I don't get this?  If I could set the name of the TAP connection that 
would be great.  Adding this stuff to the installer is one fix, but ti's 
just the same as an installer telling the user to move files around and 
set registry keys...  Just not an optimal solution, better to fix this 
"once" in ndis or colinux instead of having every installer deal with it.

>> Printing a single warning would be sufficient.
>
> In the start of colinux-daemon you can see the automatic detected 
> network adapter name. A'm afraid nobody will read this, because a 
> fresh installed TAP driver has the name "Local Area Network (2)", and 
> this is often misunderstood from similar name "Local Area Network" for 
> real Ethernet card. That is, why we say: "Please rename the name of 
> your TAP adapter into something other name, for example "TAP coLinux".
>
I can see the difference two or even 4 bytes appended to the end of a 
string can make, but I'll keep that in mind for my documentation.

>> The reason it's all blank is because this is an installer...
>> Should work wherever it's installed to.  I did see some code to assist
>> in network configuration(on this list), but I'm unsure if it corrected
>> these issues.
>
> Auto-find the right bridge will only work, if you have only one 
> Ethernet adapter running at one time, and no tuntap configured in 
> coLinux config.
For multi-homed systems we only care to get on A network...  Getting on 
the network is something every application on a multi-homed system has 
an issue with and the admin knows that...  We need not try and make his 
task more difficult by trying to do it for him.

As suggested the TAP issue should be something corrected, weather or not 
it's correctable with out removing existing features.

> The message was printed, but user would not read it while running as 
> service.
>
I see that now, should be moved to dmsg output or pollute the cmdline 
with something.

-- 
Mike Mestnik
Technical Team
___
Nagios Enterprises, INC.
Email:  mme...@na...
Web:    www.nagios.com

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

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

Hi Henry,

ok now I am a bit confused.

The colinux wiki (http://colinux.wikia.com/wiki/Network) tells me:

"The NDIS driver is new in coLinux 0.7.4. It makes use of the NDIS programming API built into windows. It works in practice exactly like the WinPcap driver, just without third party network drivers. It follows the same syntax in the configuration file as the winpcap driver, just use ndis-bridge instead of pcap-bridge"

And

"The name and mac fields are optional. If you don't specify the name parameter coLinux will use the first TAP device it finds. If you don't specify the MAC address in mac, a random one will be generated (in the range 00:FF:xx:xx:xx:xx)."

The 1st comment can be found in section NDIS (this was new to me). The 2nd comment can be found in section TAP, Installation (this is an old part of the wiki, I remember that from my first colinux contact, wich has been a couple of years ago).

Two NICs are required to create a windows bridge, in my case it seems to be quite logical to use the eth0 and tap0 for this. According to my understanding this means, that you need specify the TAP device if you want to access colinux from the network.

Could you clarify this?

Thanks
Lars



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

  Hello Lars,

> eth2=ndis-bridge,"tap0"

I wonder, that you wand to bridge the tap0? The tap0 is the TAP-Win32 
and direct connected to the coLinux. So, I would assume, you should use 
in coLinux config:
     # Bridging the real ethernet card:
     eth2=ndis-bridge,"eth0"
or
     # Bridging a Windows bridge (this is than a bride over a bridge):
     eth2=ndis-bridge,"bri0"

--
Henry

On 05.08.2010 10:38, Lars Grundei wrote:
> 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

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Henry N. <hen...@ar...>]

  On 05.08.2010 21:00, Mike Mestnik wrote:
> On 8/5/2010 2:27 PM, Henry Nestler wrote:
>>
>>> However!!! Networking still is not functional.
>>> Is there any debugging I can do?
>> Use -v 3 as option for colinux-daemon, run it on command line (not as
>> service) and read successfull all messages from network daemon.
>>
>> For more debugging disable eth0 under Linux ("ifconfig eth0 down) and
>> watch, that the ping goes truely over eth1. On Windows site you can
>> use Wireshark for watching the packets on TAP-Win32 adapter.
>>
>> You are using IP address with 169.254, I assume you have not set an IP
>> address on windows side of TAP. So, you must wait very long time after
>> start, before the device is ready. A better alternate would be to set
>> a fixed IP address for the TAP on both ends (Linux  and Windows).
>>
>> Check the IP adress on both sides and verify, that the address masked
>> with netmask matched the same network on both sides. Typicalle you
>> must use the same netmask on both sides and the starting numbers
>> should be the same (169.254.x.x) for both ends.
>>
> I'll try some of these, thank you.
> ...What would I do if every thing works file when running as an application?

Add a MAC in coLinux config, than running from command line and as 
service are identical fro the network issue.
If you leave blank the MAC, then coLinux use a random MAC, and this 
number is different between the running from command line and running as 
service.

Next step would be to use "colinux-daemon --install-service ..." and run 
it. You will have no differences.
Of curse the image files you have created should be writable for the 
Windows account "Service".


>>> eth0=ndis-bridge
>>> eth1=tuntap,,00:18:8B:26:44:88
>> Without MAC and without name of your real ethernet card you would have
>> two problems.
> The MAC should be that of the emulated card... correct?  Having this
> match the physical device would sound like ruin.

Yes, the MAC is for the guest - the Linux side.
And, to never matching a real adapter it should start with 02, not with 00.

>> 1. On startup the ndis-bride can attach to the TAP-Win32. That is a
>> loopback to coLinux self. To solve this, you should add the name of
>> real Ethernet card.
> Please add code to prevent this, only bind to a TAP-Win32 device if it's
> the only device or if it was specified by name.

This is not possible. The rule for empty name is: Using the first 
adapter, that has a link connection.
The ndis does not know what network card is your choice. The ndis-daemon 
is a separate daemon, that does not know some about the other coLinux 
network daemons. You can have WLAN cards, cable cards, VPN (also TAP-Win32).
If ndis should not use the first that it will find, then set a name into 
the config.

Other case you can sort the network order under Windows, so the 
TAP-Win32 is not the first. This is of curse nothing for your installer.

> Printing a single warning would be sufficient.

In the start of colinux-daemon you can see the automatic detected 
network adapter name. A'm afraid nobody will read this, because a fresh 
installed TAP driver has the name "Local Area Network (2)", and this is 
often misunderstood from similar name "Local Area Network" for real 
Ethernet card. That is, why we say: "Please rename the name of your TAP 
adapter into something other name, for example "TAP coLinux".

> The reason it's all blank is because this is an installer...
> Should work wherever it's installed to.  I did see some code to assist
> in network configuration(on this list), but I'm unsure if it corrected
> these issues.

Auto-find the right bridge will only work, if you have only one Ethernet 
adapter running at one time, and no tuntap configured in coLinux config.
The message was printed, but user would not read it while running as 
service.

-- 
Henry N.

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Mike M. <mme...@na...>]

On 8/5/2010 2:27 PM, Henry Nestler wrote:
>  On 05.08.2010 17:36, Mike Mestnik wrote:
>> I finally got this working, using...
>> # echo -ne 'CoLinuxDriver\0tap0801co\0\0' | hexdump -ve '4/1 "&i1 %3u,"
>> "\\\n"'
>>         System::Call "*(&i1  67,&i1 111,&i1  76,&i1 105,\
>> &i1 110,&i1 117,&i1 120,&i1  68,\
>> &i1 114,&i1 105,&i1 118,&i1 101,\
>> &i1 114,&i1   0,&i1 116,&i1  97,\
>> &i1 112,&i1  48,&i1  56,&i1  48,\
>> &i1  49,&i1  99,&i1 111,&i1   0,\
>> &i1   0) i .R1"
>>         System::Call 'advapi32::CreateServiceA(i r4, t r2, t R7, i
>> ${SERVICE_ALL_ACCESS}, \
>>                                                i R4, i R5, i 0, t R6, n,
>> n, i $R1, $R2, $R3) i.r6'
>
> Hui, what an interesting hack :))
>
>> However!!! Networking still is not functional.
>> Is there any debugging I can do?
>
> Use -v 3 as option for colinux-daemon, run it on command line (not as 
> service) and read successfull all messages from network daemon.
>
Bow to the gods of both Windows and Linux.

As you indicated every one garbed the wrong interface.

> For more debugging disable eth0 under Linux ("ifconfig eth0 down) and 
> watch, that the ping goes truely over eth1. On Windows site you can 
> use Wireshark for watching the packets on TAP-Win32 adapter.
>
> You are using IP address with 169.254, I assume you have not set an IP 
> address on windows side of TAP. So, you must wait very long time after 
> start, before the device is ready. A better alternate would be to set 
> a fixed IP address for the TAP on both ends (Linux  and Windows).
>
> Check the IP adress on both sides and verify, that the address masked 
> with netmask matched the same network on both sides. Typicalle you 
> must use the same netmask on both sides and the starting numbers 
> should be the same (169.254.x.x) for both ends.
>
>> eth0=ndis-bridge
>> eth1=tuntap,,00:18:8B:26:44:88
>
> Without MAC and without name of your real ethernet card you would have 
> two problems.
> 1. On startup the ndis-bride can attach to the TAP-Win32. That is a 
> loopback to coLinux self. To solve this, you should add the name of 
> real Ethernet card.
> 2. Without MAC in the config, the random MAC can trigger sometimes the 
> udev-system to create a new ethernet number. It is no guarantee, that 
> eth0 will come up. Sometimes it will renamed to eth2, eth3 and so on. 
> You can see it under Linux in boot messages and in /proc/net/dev
>


-- 
Mike Mestnik
Technical Team
___
Nagios Enterprises, INC.
Email:  mme...@na...
Web:    www.nagios.com

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Mike M. <mme...@na...>]

On 8/5/2010 2:27 PM, Henry Nestler wrote:
>  On 05.08.2010 17:36, Mike Mestnik wrote:
>> I finally got this working, using...
>> # echo -ne 'CoLinuxDriver\0tap0801co\0\0' | hexdump -ve '4/1 "&i1 %3u,"
>> "\\\n"'
>>         System::Call "*(&i1  67,&i1 111,&i1  76,&i1 105,\
>> &i1 110,&i1 117,&i1 120,&i1  68,\
>> &i1 114,&i1 105,&i1 118,&i1 101,\
>> &i1 114,&i1   0,&i1 116,&i1  97,\
>> &i1 112,&i1  48,&i1  56,&i1  48,\
>> &i1  49,&i1  99,&i1 111,&i1   0,\
>> &i1   0) i .R1"
>>         System::Call 'advapi32::CreateServiceA(i r4, t r2, t R7, i
>> ${SERVICE_ALL_ACCESS}, \
>>                                                i R4, i R5, i 0, t R6, n,
>> n, i $R1, $R2, $R3) i.r6'
>
> Hui, what an interesting hack :))
>
>> However!!! Networking still is not functional.
>> Is there any debugging I can do?
>
> Use -v 3 as option for colinux-daemon, run it on command line (not as 
> service) and read successfull all messages from network daemon.
>
> For more debugging disable eth0 under Linux ("ifconfig eth0 down) and 
> watch, that the ping goes truely over eth1. On Windows site you can 
> use Wireshark for watching the packets on TAP-Win32 adapter.
>
> You are using IP address with 169.254, I assume you have not set an IP 
> address on windows side of TAP. So, you must wait very long time after 
> start, before the device is ready. A better alternate would be to set 
> a fixed IP address for the TAP on both ends (Linux  and Windows).
>
> Check the IP adress on both sides and verify, that the address masked 
> with netmask matched the same network on both sides. Typicalle you 
> must use the same netmask on both sides and the starting numbers 
> should be the same (169.254.x.x) for both ends.
>
I'll try some of these, thank you.
...What would I do if every thing works file when running as an application?
>> eth0=ndis-bridge
>> eth1=tuntap,,00:18:8B:26:44:88
>
> Without MAC and without name of your real ethernet card you would have 
> two problems.
The MAC should be that of the emulated card... correct?  Having this 
match the physical device would sound like ruin.
> 1. On startup the ndis-bride can attach to the TAP-Win32. That is a 
> loopback to coLinux self. To solve this, you should add the name of 
> real Ethernet card.
Please add code to prevent this, only bind to a TAP-Win32 device if it's 
the only device or if it was specified by name.  Printing a single 
warning would be sufficient.

The reason it's all blank is because this is an installer...
Should work wherever it's installed to.  I did see some code to assist 
in network configuration(on this list), but I'm unsure if it corrected 
these issues.

I'd be interested in doing this for future versions, but for now just to 
get something that would work some of the time would be enough.

> 2. Without MAC in the config, the random MAC can trigger sometimes the 
> udev-system to create a new ethernet number. It is no guarantee, that 
> eth0 will come up. Sometimes it will renamed to eth2, eth3 and so on. 
> You can see it under Linux in boot messages and in /proc/net/dev
>
I've disabled this feature ;)

-- 
Mike Mestnik
Technical Team
___
Nagios Enterprises, INC.
Email:  mme...@na...
Web:    www.nagios.com

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Henry N. <hen...@ar...>]

  On 05.08.2010 17:36, Mike Mestnik wrote:
> I finally got this working, using...
> # echo -ne 'CoLinuxDriver\0tap0801co\0\0' | hexdump -ve '4/1 "&i1 %3u,"
> "\\\n"'
>         System::Call "*(&i1  67,&i1 111,&i1  76,&i1 105,\
> &i1 110,&i1 117,&i1 120,&i1  68,\
> &i1 114,&i1 105,&i1 118,&i1 101,\
> &i1 114,&i1   0,&i1 116,&i1  97,\
> &i1 112,&i1  48,&i1  56,&i1  48,\
> &i1  49,&i1  99,&i1 111,&i1   0,\
> &i1   0) i .R1"
>         System::Call 'advapi32::CreateServiceA(i r4, t r2, t R7, i
> ${SERVICE_ALL_ACCESS}, \
>                                                i R4, i R5, i 0, t R6, n,
> n, i $R1, $R2, $R3) i.r6'

Hui, what an interesting hack :))

> However!!! Networking still is not functional.
> Is there any debugging I can do?

Use -v 3 as option for colinux-daemon, run it on command line (not as 
service) and read successfull all messages from network daemon.

For more debugging disable eth0 under Linux ("ifconfig eth0 down) and 
watch, that the ping goes truely over eth1. On Windows site you can use 
Wireshark for watching the packets on TAP-Win32 adapter.

You are using IP address with 169.254, I assume you have not set an IP 
address on windows side of TAP. So, you must wait very long time after 
start, before the device is ready. A better alternate would be to set a 
fixed IP address for the TAP on both ends (Linux  and Windows).

Check the IP adress on both sides and verify, that the address masked 
with netmask matched the same network on both sides. Typicalle you must 
use the same netmask on both sides and the starting numbers should be 
the same (169.254.x.x) for both ends.

> eth0=ndis-bridge
> eth1=tuntap,,00:18:8B:26:44:88

Without MAC and without name of your real ethernet card you would have 
two problems.
1. On startup the ndis-bride can attach to the TAP-Win32. That is a 
loopback to coLinux self. To solve this, you should add the name of real 
Ethernet card.
2. Without MAC in the config, the random MAC can trigger sometimes the 
udev-system to create a new ethernet number. It is no guarantee, that 
eth0 will come up. Sometimes it will renamed to eth2, eth3 and so on. 
You can see it under Linux in boot messages and in /proc/net/dev

-- 
Henry N.

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

[Henry N. <hen...@ar...>]

  Hello Lars,

> eth2=ndis-bridge,"tap0"

I wonder, that you wand to bridge the tap0? The tap0 is the TAP-Win32 
and direct connected to the coLinux. So, I would assume, you should use 
in coLinux config:
     # Bridging the real ethernet card:
     eth2=ndis-bridge,"eth0"
or
     # Bridging a Windows bridge (this is than a bride over a bridge):
     eth2=ndis-bridge,"bri0"

--
Henry

On 05.08.2010 10:38, Lars Grundei wrote:
> 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

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Mike M. <mme...@na...>]

On 8/3/2010 5:53 PM, Henry Nestler wrote:
>  Hello Mike,
>
> On 03.08.2010 22:19, Mike Mestnik wrote:
>> On 8/3/2010 4:49 PM, Henry Nestler wrote: Hello Mike,
>>> On 02.08.2010 18:40, Mike Mestnik wrote:
>>>>     Push "create"
>>>>     Push "Nagios Core"
>>>>     Push 'path="C:\Program Files\Nagios Core\colinux-daemon.exe"
>>>> @NagiosCore.conf --run-service "Nagios
>>>> Core";autostart=1;depend=CoLinuxDriver;display=Nagios
>>>> Core;description=Nagios Core Linux Service, this service manages a
>>>> running instance of linux.;'
>>>>     Call Service
>>>>     Pop $0 ;response
>>> This part us ugly, wrong and will not run on all destinations.
>>>
>>> * Please never use "C:\Program Files\" directly! Please use the
>>> install path "$INSTDIR".
>>> * You should use the coLinux service installer. Or you should complete
>>> adding all dependensies. You are using TAP? Then should add
>>> "tap0801co". The colinux-daemon will parse your config and adds
>>> dependencies automatically, if you use such device.
>> Sorry to still bother, but after looking at these resources I can't seam
>> to discover how this would work as an array.
>> http://nsis.sourceforge.net/NSIS_Service_Lib
>> http://msdn.microsoft.com/en-us/library/ms682450%28VS.85%29.aspx
>>
>> ";depend=tap0801co,CoLinuxDriver;"
>> is my first guess.
>
I finally got this working, using...
# echo -ne 'CoLinuxDriver\0tap0801co\0\0' | hexdump -ve '4/1 " &i1 %3u," 
"\\\n"'
       System::Call "*(&i1  67, &i1 111, &i1  76, &i1 105,\
&i1 110, &i1 117, &i1 120, &i1  68,\
&i1 114, &i1 105, &i1 118, &i1 101,\
&i1 114, &i1   0, &i1 116, &i1  97,\
&i1 112, &i1  48, &i1  56, &i1  48,\
&i1  49, &i1  99, &i1 111, &i1   0,\
&i1   0) i .R1"
       System::Call 'advapi32::CreateServiceA(i r4, t r2, t R7, i 
${SERVICE_ALL_ACCESS}, \
                                              i R4, i R5, i 0, t R6, n, 
n, i $R1, $R2, $R3) i.r6'


However!!! Networking still is not functional.
Is there any debugging I can do?

> Think, it is not supported by this addon.
> The right string for dependency names in CreateService is 
> "CoLinuxDriver\0tap0801co\0\0".
> The delimiter between strings is "\0" and the string termination is 
> "\0\0".
> This would not work with the "StrCpy" in servicelib.nsh, I think. 
> StrCpy would stop on first 00h.
>
> In other case, you can assume, that coLinuxDriver will faster load as 
> the network driver. coLinuxDriver has no more other dependency. Tap 
> driver needs a complete network being up. So, adding only "tap0801co" 
> would be enough for delaying coLinux startup.
>


-- 
Mike Mestnik
Technical Team
___
Nagios Enterprises, INC.
Email:  mme...@na...
Web:    www.nagios.com

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.

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Mike M. <mme...@na...>]

On 8/3/2010 6:43 PM, Henry Nestler wrote:
>  hello Mike,
>
> On 03.08.2010 22:06, Mike Mestnik wrote:
>> On 8/3/2010 4:49 PM, Henry Nestler wrote:
>>> On 02.08.2010 18:40, Mike Mestnik wrote:
>>>>     Push "create"
>>>>     Push "Nagios Core"
>>>>     Push 'path="C:\Program Files\Nagios Core\colinux-daemon.exe"
>>>> @NagiosCore.conf --run-service "Nagios
>>>> Core";autostart=1;depend=CoLinuxDriver;display=Nagios
>>>> Core;description=Nagios Core Linux Service, this service manages a
>>>> running instance of linux.;'
>>>>     Call Service
>>>>     Pop $0 ;response
>>> This part us ugly, wrong and will not run on all destinations.
>>>
>>> * Please never use "C:\Program Files\" directly! Please use the
>>> install path "$INSTDIR".
>>> * You should use the coLinux service installer.
>> Can I set autostart using the installer?
>
> No. The user should run it manually at first time.
> If it's running good, the user can change the mode simply in service 
> control manager.
> If the automatic start would crash on every boot, it is difficult for 
> user to stop this. (with "safe mode", removing service, ...).
>
The intended audience is users who have never seen the service control 
manager and wouldn't understand it if they did...  That and "Automation 
is key." -- Mike Mestnik

-- 
Mike Mestnik
Technical Team
___
Nagios Enterprises, INC.
Email:  mme...@na...
Web:    www.nagios.com

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Henry N. <hen...@ar...>]

  hello Mike,

On 03.08.2010 22:06, Mike Mestnik wrote:
> On 8/3/2010 4:49 PM, Henry Nestler wrote:
>> On 02.08.2010 18:40, Mike Mestnik wrote:
>>>     Push "create"
>>>     Push "Nagios Core"
>>>     Push 'path="C:\Program Files\Nagios Core\colinux-daemon.exe"
>>> @NagiosCore.conf --run-service "Nagios
>>> Core";autostart=1;depend=CoLinuxDriver;display=Nagios
>>> Core;description=Nagios Core Linux Service, this service manages a
>>> running instance of linux.;'
>>>     Call Service
>>>     Pop $0 ;response
>> This part us ugly, wrong and will not run on all destinations.
>>
>> * Please never use "C:\Program Files\" directly! Please use the
>> install path "$INSTDIR".
>> * You should use the coLinux service installer.
> Can I set autostart using the installer?

No. The user should run it manually at first time.
If it's running good, the user can change the mode simply in service 
control manager.
If the automatic start would crash on every boot, it is difficult for 
user to stop this. (with "safe mode", removing service, ...).

-- 
Henry N.

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Mike M. <mme...@na...>]

On 8/3/2010 5:53 PM, Henry Nestler wrote:
>  Hello Mike,
>
> On 03.08.2010 22:19, Mike Mestnik wrote:
>> On 8/3/2010 4:49 PM, Henry Nestler wrote: Hello Mike,
>>> On 02.08.2010 18:40, Mike Mestnik wrote:
>>>>     Push "create"
>>>>     Push "Nagios Core"
>>>>     Push 'path="C:\Program Files\Nagios Core\colinux-daemon.exe"
>>>> @NagiosCore.conf --run-service "Nagios
>>>> Core";autostart=1;depend=CoLinuxDriver;display=Nagios
>>>> Core;description=Nagios Core Linux Service, this service manages a
>>>> running instance of linux.;'
>>>>     Call Service
>>>>     Pop $0 ;response
>>> This part us ugly, wrong and will not run on all destinations.
>>>
>>> * Please never use "C:\Program Files\" directly! Please use the
>>> install path "$INSTDIR".
>>> * You should use the coLinux service installer. Or you should complete
>>> adding all dependensies. You are using TAP? Then should add
>>> "tap0801co". The colinux-daemon will parse your config and adds
>>> dependencies automatically, if you use such device.
>> Sorry to still bother, but after looking at these resources I can't seam
>> to discover how this would work as an array.
>> http://nsis.sourceforge.net/NSIS_Service_Lib
>> http://msdn.microsoft.com/en-us/library/ms682450%28VS.85%29.aspx
>>
>> ";depend=tap0801co,CoLinuxDriver;"
>> is my first guess.
>
> Think, it is not supported by this addon.
> The right string for dependency names in CreateService is 
> "CoLinuxDriver\0tap0801co\0\0".
> The delimiter between strings is "\0" and the string termination is 
> "\0\0".
> This would not work with the "StrCpy" in servicelib.nsh, I think. 
> StrCpy would stop on first 00h.
>
> In other case, you can assume, that coLinuxDriver will faster load as 
> the network driver. coLinuxDriver has no more other dependency. Tap 
> driver needs a complete network being up. So, adding only "tap0801co" 
> would be enough for delaying coLinux startup.
>
I see, but the coLinux driver might not start at all.  That and this is 
not sysv, it's windows, keyboard and mouse drivers are known to not load 
when expected, why expect anything else to function on time?

This is frailly standard, it's an array of ansi strings.  
http://www.java2s.com/Code/C/Data-Type/Arraysofstrings.htm

As you are correct StrCpy will likely not work with an C Data-Type like 
a string, let alone an array of C strings.  NSIS is a higher level 
language, so this atom would need to be mapped to a higher level 
construct.  As this whole structure is, with '\0' being replaced with 
';' I'd just assumed this case too was handled...  Perhaps by another 
interpreter, like VB...

Sorry for the NSIS specific question!!!

-- 
Mike Mestnik
Technical Team
___
Nagios Enterprises, INC.
Email:  mme...@na...
Web:    www.nagios.com

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Henry N. <hen...@ar...>]

  Hello Mike,

On 03.08.2010 22:19, Mike Mestnik wrote:
> On 8/3/2010 4:49 PM, Henry Nestler wrote: Hello Mike,
>> On 02.08.2010 18:40, Mike Mestnik wrote:
>>>     Push "create"
>>>     Push "Nagios Core"
>>>     Push 'path="C:\Program Files\Nagios Core\colinux-daemon.exe"
>>> @NagiosCore.conf --run-service "Nagios
>>> Core";autostart=1;depend=CoLinuxDriver;display=Nagios
>>> Core;description=Nagios Core Linux Service, this service manages a
>>> running instance of linux.;'
>>>     Call Service
>>>     Pop $0 ;response
>> This part us ugly, wrong and will not run on all destinations.
>>
>> * Please never use "C:\Program Files\" directly! Please use the
>> install path "$INSTDIR".
>> * You should use the coLinux service installer. Or you should complete
>> adding all dependensies. You are using TAP? Then should add
>> "tap0801co". The colinux-daemon will parse your config and adds
>> dependencies automatically, if you use such device.
> Sorry to still bother, but after looking at these resources I can't seam
> to discover how this would work as an array.
> http://nsis.sourceforge.net/NSIS_Service_Lib
> http://msdn.microsoft.com/en-us/library/ms682450%28VS.85%29.aspx
>
> ";depend=tap0801co,CoLinuxDriver;"
> is my first guess.

Think, it is not supported by this addon.
The right string for dependency names in CreateService is 
"CoLinuxDriver\0tap0801co\0\0".
The delimiter between strings is "\0" and the string termination is "\0\0".
This would not work with the "StrCpy" in servicelib.nsh, I think. StrCpy 
would stop on first 00h.

In other case, you can assume, that coLinuxDriver will faster load as 
the network driver. coLinuxDriver has no more other dependency. Tap 
driver needs a complete network being up. So, adding only "tap0801co" 
would be enough for delaying coLinux startup.

-- 
Henry N.

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Mike M. <mme...@na...>]

On 8/3/2010 4:49 PM, Henry Nestler wrote:
>  Hello Mike,
>
> On 02.08.2010 18:40, Mike Mestnik wrote:
>> I'm able to ping Windows from coLinux, but Windows dose not attempt to
>> arp or ping back.  Most odd, tcpdump under colinux shows only it's own
>> traffic and ping replies.  I'm using ipv4ll for the tap interface on the
>> windows side and a static 169.254 address in coLinux.
>
> If you are using Windows 7 or XP-SP3, then remember to allow Ping in 
> your Windows firewall.
>
>> eth0=ndis-bridge
>>
>> # Tuntap as private network between guest and host on second linux 
>> device
>> eth1=tuntap,,00:18:8B:26:44:88
>
> For testing network interfaces, you should enable only one interface. 
> So, please disable eth0 ("ifconfig eth0 down") at the time you are 
> testing tap on eth1. Other case you can not see the packet way right.
>
> Please start the MAC with 02: for personal use (00: is reserved for 
> real hardware cards). And I hope, this MAC number does not exist some 
> there in your network! Using fixed MAC in an installer is a highly 
> risk. Every body should have its one unique MAC. It would be better to 
> leave this option out and let coLinux set a random number. The random 
> number will generate only ones at first start, and is stored in 
> registry for later use.
>
>>    Push "create"
>>    Push "Nagios Core"
>>    Push 'path="C:\Program Files\Nagios Core\colinux-daemon.exe" 
>> @NagiosCore.conf --run-service "Nagios 
>> Core";autostart=1;depend=CoLinuxDriver;display=Nagios 
>> Core;description=Nagios Core Linux Service, this service manages a 
>> running instance of linux.;'
>>    Call Service
>>    Pop $0 ;response
>
> This part us ugly, wrong and will not run on all destinations.
>
> * Please never use "C:\Program Files\" directly! Please use the 
> install path "$INSTDIR".
> * You should use the coLinux service installer. Or you should complete 
> adding all dependensies. You are using TAP? Then should add 
> "tap0801co". The colinux-daemon will parse your config and adds 
> dependencies automatically, if you use such device.
Sorry to still bother, but after looking at these resources I can't seam 
to discover how this would work as an array.
http://nsis.sourceforge.net/NSIS_Service_Lib
http://msdn.microsoft.com/en-us/library/ms682450%28VS.85%29.aspx

";depend=tap0801co,CoLinuxDriver;"
is my first guess.

> * You have not used full path to "NagiosCore.conf"?
>


-- 
Mike Mestnik
Technical Team
___
Nagios Enterprises, INC.
Email:  mme...@na...
Web:    www.nagios.com

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Mike M. <mme...@na...>]

On 8/3/2010 4:49 PM, Henry Nestler wrote:
>  Hello Mike,
>
> On 02.08.2010 18:40, Mike Mestnik wrote:
>> I'm able to ping Windows from coLinux, but Windows dose not attempt to
>> arp or ping back.  Most odd, tcpdump under colinux shows only it's own
>> traffic and ping replies.  I'm using ipv4ll for the tap interface on the
>> windows side and a static 169.254 address in coLinux.
>
> If you are using Windows 7 or XP-SP3, then remember to allow Ping in 
> your Windows firewall.
>
>> eth0=ndis-bridge
>>
>> # Tuntap as private network between guest and host on second linux 
>> device
>> eth1=tuntap,,00:18:8B:26:44:88
>
> For testing network interfaces, you should enable only one interface. 
> So, please disable eth0 ("ifconfig eth0 down") at the time you are 
> testing tap on eth1. Other case you can not see the packet way right.
>
> Please start the MAC with 02: for personal use (00: is reserved for 
> real hardware cards). And I hope, this MAC number does not exist some 
> there in your network! Using fixed MAC in an installer is a highly 
> risk. Every body should have its one unique MAC. It would be better to 
> leave this option out and let coLinux set a random number. The random 
> number will generate only ones at first start, and is stored in 
> registry for later use.
>
>>    Push "create"
>>    Push "Nagios Core"
>>    Push 'path="C:\Program Files\Nagios Core\colinux-daemon.exe" 
>> @NagiosCore.conf --run-service "Nagios 
>> Core";autostart=1;depend=CoLinuxDriver;display=Nagios 
>> Core;description=Nagios Core Linux Service, this service manages a 
>> running instance of linux.;'
>>    Call Service
>>    Pop $0 ;response
>
> This part us ugly, wrong and will not run on all destinations.
>
> * Please never use "C:\Program Files\" directly! Please use the 
> install path "$INSTDIR".
> * You should use the coLinux service installer.
Can I set autostart using the installer?  The description is optional, 
but it's nice.

> * You have not used full path to "NagiosCore.conf"?
>


-- 
Mike Mestnik
Technical Team
___
Nagios Enterprises, INC.
Email:  mme...@na...
Web:    www.nagios.com

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Mike M. <mme...@na...>]

On 8/3/2010 4:49 PM, Henry Nestler wrote:
>  Hello Mike,
>
> On 02.08.2010 18:40, Mike Mestnik wrote:
>> I'm able to ping Windows from coLinux, but Windows dose not attempt to
>> arp or ping back.  Most odd, tcpdump under colinux shows only it's own
>> traffic and ping replies.  I'm using ipv4ll for the tap interface on the
>> windows side and a static 169.254 address in coLinux.
>
> If you are using Windows 7 or XP-SP3, then remember to allow Ping in 
> your Windows firewall.
>
>> eth0=ndis-bridge
>>
>> # Tuntap as private network between guest and host on second linux 
>> device
>> eth1=tuntap,,00:18:8B:26:44:88
>
> For testing network interfaces, you should enable only one interface. 
> So, please disable eth0 ("ifconfig eth0 down") at the time you are 
> testing tap on eth1. Other case you can not see the packet way right.
>
> Please start the MAC with 02: for personal use (00: is reserved for 
> real hardware cards). And I hope, this MAC number does not exist some 
> there in your network! Using fixed MAC in an installer is a highly 
> risk. Every body should have its one unique MAC. It would be better to 
> leave this option out and let coLinux set a random number. The random 
> number will generate only ones at first start, and is stored in 
> registry for later use.
>
>>    Push "create"
>>    Push "Nagios Core"
>>    Push 'path="C:\Program Files\Nagios Core\colinux-daemon.exe" 
>> @NagiosCore.conf --run-service "Nagios 
>> Core";autostart=1;depend=CoLinuxDriver;display=Nagios 
>> Core;description=Nagios Core Linux Service, this service manages a 
>> running instance of linux.;'
>>    Call Service
>>    Pop $0 ;response
>
> This part us ugly, wrong and will not run on all destinations.
>
> * Please never use "C:\Program Files\" directly! Please use the 
> install path "$INSTDIR".
Opps.

> * You should use the coLinux service installer. Or you should complete 
> adding all dependensies. You are using TAP? Then should add 
> "tap0801co". The colinux-daemon will parse your config and adds 
> dependencies automatically, if you use such device.
Yay ! :)

> * You have not used full path to "NagiosCore.conf"?
>
Correct, in testing this didn't work.  I'll try again.

-- 
Mike Mestnik
Technical Team
___
Nagios Enterprises, INC.
Email:  mme...@na...
Web:    www.nagios.com

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Henry N. <hen...@ar...>]

  Hello Mike,

On 02.08.2010 18:40, Mike Mestnik wrote:
> I'm able to ping Windows from coLinux, but Windows dose not attempt to
> arp or ping back.  Most odd, tcpdump under colinux shows only it's own
> traffic and ping replies.  I'm using ipv4ll for the tap interface on the
> windows side and a static 169.254 address in coLinux.

If you are using Windows 7 or XP-SP3, then remember to allow Ping in 
your Windows firewall.

> eth0=ndis-bridge
>
> # Tuntap as private network between guest and host on second linux device
> eth1=tuntap,,00:18:8B:26:44:88

For testing network interfaces, you should enable only one interface. 
So, please disable eth0 ("ifconfig eth0 down") at the time you are 
testing tap on eth1. Other case you can not see the packet way right.

Please start the MAC with 02: for personal use (00: is reserved for real 
hardware cards). And I hope, this MAC number does not exist some there 
in your network! Using fixed MAC in an installer is a highly risk. Every 
body should have its one unique MAC. It would be better to leave this 
option out and let coLinux set a random number. The random number will 
generate only ones at first start, and is stored in registry for later use.

>    Push "create"
>    Push "Nagios Core"
>    Push 'path="C:\Program Files\Nagios Core\colinux-daemon.exe" @NagiosCore.conf --run-service "Nagios Core";autostart=1;depend=CoLinuxDriver;display=Nagios Core;description=Nagios Core Linux Service, this service manages a running instance of linux.;'
>    Call Service
>    Pop $0 ;response

This part us ugly, wrong and will not run on all destinations.

* Please never use "C:\Program Files\" directly! Please use the install 
path "$INSTDIR".
* You should use the coLinux service installer. Or you should complete 
adding all dependensies. You are using TAP? Then should add "tap0801co". 
The colinux-daemon will parse your config and adds dependencies 
automatically, if you use such device.
* You have not used full path to "NagiosCore.conf"?

-- 
Henry N.

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

[Henry N. <hen...@ar...>]

  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.

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Mike M. <mme...@na...>]

On 8/2/2010 9:47 PM, Mike Frysinger wrote:
> On Mon, Aug 2, 2010 at 13:22, Mike Mestnik wrote:
>    
>> On 8/2/2010 1:18 PM, Mike Frysinger wrote:
>>      
>>> On Mon, Aug 2, 2010 at 13:07, Mike Mestnik wrote:
>>>        
>>>> This looks to be a vary full featured installer, but I can't determine a
>>>> solution to the issue I'm reporting.  For my installation "ndis>
>>>>   winpcap"
>>>> so winpcap was removed from the install.
>>>>          
>>> i guess i missed what you were talking about.  i thought you were
>>> having problems configuring the taps between windows and colinux.  i
>>> dont have a clue wrt ndis vs winpcap; sorry.
>>>        
>> That's correct I am.  I'm confused, did you mean to say that wpcap could
>> replace taps?  I don't feel that wpcap is a solution
>>      
> the wiki documents that wpcap is the fastest solution.
> http://colinux.wikia.com/wiki/Network
>
>    
That may vary well be and I see the document...  However WinPcap lives 
on-top of NDIS, so any performance impact that NDIS supplies should 
still exist.  There is no clear documentation on what part of 
NDIS(driver or system) that winpcap uses, but based on it's absence in 
the Network Connection's screen I'd guess it uses the system API to 
access a driver so I don't clearly see the difference from what coLinux 
must do.

I could completely not know what I'm talking about.
>> and I don't feel that
>> your patch corrects the issue I was having with taps.
>>      
> the point of my patch was to show how to configure the network
> interfaces after they've already been created.  that's all.
> -mike
>    
Ahh, so I could do network configuration as part of my installer...  I 
saw that and it looked interesting, I didn't quickly grasp how these 
variables were passed down to the init scripts living in a filesystem 
image.  I can only imagine they pass through /proc/cmdline.

This would not solve my issue though, the problem is post-configuration 
AFAIK.

-- 
Mike Mestnik
Technical Team
___
Nagios Enterprises, INC.
Email:  mme...@na...
Web:    www.nagios.com

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

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

Hello everybody,

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

Can someone tell me what is going wrong?

Thanks for your support
Lars

PS: Extract from the config file:
-----------------------------
# Slirp for internet connection (outgoing)
# Inside running coLinux configure eth0 with this static settings:
# ipaddress 10.0.2.15   broadcast  10.0.2.255   netmask 255.255.255.0
# gateway   10.0.2.2    nameserver 10.0.2.3
#eth0=slirp

# Tuntap as private network between guest and host on second linux device
#eth1=tuntap

# brigded networks
eth2=ndis-bridge,"tap0"
-----------------------------

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Mike F. <vap...@gm...>]

On Mon, Aug 2, 2010 at 13:22, Mike Mestnik wrote:
> On 8/2/2010 1:18 PM, Mike Frysinger wrote:
>> On Mon, Aug 2, 2010 at 13:07, Mike Mestnik wrote:
>>> This looks to be a vary full featured installer, but I can't determine a
>>> solution to the issue I'm reporting.  For my installation "ndis>
>>>  winpcap"
>>> so winpcap was removed from the install.
>>
>> i guess i missed what you were talking about.  i thought you were
>> having problems configuring the taps between windows and colinux.  i
>> dont have a clue wrt ndis vs winpcap; sorry.
>
> That's correct I am.  I'm confused, did you mean to say that wpcap could
> replace taps?  I don't feel that wpcap is a solution

the wiki documents that wpcap is the fastest solution.
http://colinux.wikia.com/wiki/Network

> and I don't feel that
> your patch corrects the issue I was having with taps.

the point of my patch was to show how to configure the network
interfaces after they've already been created.  that's all.
-mike

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Mike M. <mme...@na...>]

On 8/2/2010 1:18 PM, Mike Frysinger wrote:
> On Mon, Aug 2, 2010 at 13:07, Mike Mestnik wrote:
>    
>> What was your motivation for disabling the [1]embedded winpcap installer and
>> replacing it with an execwait?  I would recommend that you Embed the putty
>> and xming installers in the same fashion that the WinPcap installer was.
>>      
> the current coLinux method involves downloading the different
> installers on the fly.  i'm not interested in that ... my installer is
> one download and includes everything you'll need.  and with the
> compression, i dont think the larger file sizes are too much bigger to
> really matter.
>
> if there is a way to embed the installer and use the "official"
> method, then i'll certainly take a look.
>
>    
>> This looks to be a vary full featured installer, but I can't determine a
>> solution to the issue I'm reporting.  For my installation "ndis>  winpcap"
>> so winpcap was removed from the install.
>>      
> i guess i missed what you were talking about.  i thought you were
> having problems configuring the taps between windows and colinux.  i
> dont have a clue wrt ndis vs winpcap; sorry.
> -mike
>
>    
That's correct I am.  I'm confused, did you mean to say that wpcap could 
replace taps?  I don't feel that wpcap is a solution and I don't feel 
that your patch corrects the issue I was having with taps.

-- 
Mike Mestnik
Technical Team
___
Nagios Enterprises, INC.
Email:  mme...@na...
Web:    www.nagios.com

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Mike F. <vap...@gm...>]

On Mon, Aug 2, 2010 at 13:07, Mike Mestnik wrote:
> What was your motivation for disabling the [1]embedded winpcap installer and
> replacing it with an execwait?  I would recommend that you Embed the putty
> and xming installers in the same fashion that the WinPcap installer was.

the current coLinux method involves downloading the different
installers on the fly.  i'm not interested in that ... my installer is
one download and includes everything you'll need.  and with the
compression, i dont think the larger file sizes are too much bigger to
really matter.

if there is a way to embed the installer and use the "official"
method, then i'll certainly take a look.

> This looks to be a vary full featured installer, but I can't determine a
> solution to the issue I'm reporting.  For my installation "ndis > winpcap"
> so winpcap was removed from the install.

i guess i missed what you were talking about.  i thought you were
having problems configuring the taps between windows and colinux.  i
dont have a clue wrt ndis vs winpcap; sorry.
-mike

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Mike M. <mme...@na...>]

On 8/2/2010 12:55 PM, Mike Frysinger wrote:
> On Mon, Aug 2, 2010 at 12:40, Mike Mestnik wrote:
>    
>>   I wanted to write a custom installer for Nagios running under coLinux.
>>   This worked great... although the tap adapter doesn't operate.  I was
>> wondering if I could seek some assistance from an nsis developer?
>>
>> I'd also wonder if this was common for networking to not function, unless
>> you used Slirp?
>> After researching Slirp I'm thinking it should have been my first choice.
>>
>> Never the less it would be grand if my first attempt could be working.
>>
>> I'm able to ping Windows from coLinux, but Windows dose not attempt to arp
>> or ping back.  Most odd, tcpdump under colinux shows only it's own traffic
>> and ping replies.  I'm using ipv4ll for the tap interface on the windows
>> side and a static 169.254 address in coLinux .
>>      
> checkout the NSIS installer patch ive written here:
> http://blackfin.uclinux.org/gf/project/bfin-colinux/scmsvn/trunk/patches/
>
> this installer will install winpcap, the tap driver (already part of
> colinux), prompt the user for the desired IP addresses, and then take
> care of the setup for them.
>    
What was your motivation for disabling the [1]embedded winpcap installer 
and replacing it with an execwait?  I would recommend that you Embed the 
putty and xming installers in the same fashion that the WinPcap 
installer was.

1. http://nsis.sourceforge.net/Embedding_other_installers

This looks to be a vary full featured installer, but I can't determine a 
solution to the issue I'm reporting.  For my installation "ndis > 
winpcap" so winpcap was removed from the install.

I feel there is something wrong with the tap adapter, not sure it's an 
NSIS issue.

> ive tested this under win2000/winxp/vista and know it works there.
> presumably it also works under win7 since it'll be close to vista, but
> i dont have any win7 32bit installs to test with :x.
> -mike
> -mike
>
>    


-- 
Mike Mestnik
Technical Team
___
Nagios Enterprises, INC.
Email:  mme...@na...
Web:    www.nagios.com

Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

[Mike F. <vap...@gm...>]

On Mon, Aug 2, 2010 at 12:40, Mike Mestnik wrote:
>  I wanted to write a custom installer for Nagios running under coLinux.
>  This worked great... although the tap adapter doesn't operate.  I was
> wondering if I could seek some assistance from an nsis developer?
>
> I'd also wonder if this was common for networking to not function, unless
> you used Slirp?
> After researching Slirp I'm thinking it should have been my first choice.
>
> Never the less it would be grand if my first attempt could be working.
>
> I'm able to ping Windows from coLinux, but Windows dose not attempt to arp
> or ping back.  Most odd, tcpdump under colinux shows only it's own traffic
> and ping replies.  I'm using ipv4ll for the tap interface on the windows
> side and a static 169.254 address in coLinux .

checkout the NSIS installer patch ive written here:
http://blackfin.uclinux.org/gf/project/bfin-colinux/scmsvn/trunk/patches/

this installer will install winpcap, the tap driver (already part of
colinux), prompt the user for the desired IP addresses, and then take
care of the setup for them.

ive tested this under win2000/winxp/vista and know it works there.
presumably it also works under win7 since it'll be close to vista, but
i dont have any win7 32bit installs to test with :x.
-mike
-mike