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.