Re: [coLinux-users] performance

[Mitch B. <wm...@ag...>]

I am using bridged networking with 20041002.  Network adapter matching 
is different between 20041002 and earlier snapshots.  The matched name 
used to be an internal name for the adapter, but now the name is the 
same one that is displayed underneath the connection icon in the Windows 
"Network Connections" window.  It is the name that Windows lets you 
change by right-clicking the connection icon and selecting "Rename".

  For example, for 20040910 my colinux.xml file used to say:

       <network index="0" type="bridged" name="Broadcom NetXtreme"/>

but now with 20041002 it says:

       <network index="0" type="bridged" name="Local Area Connection" />

The startup messages in the CMD window contain a list of the names that 
coLinux tries to match against.

Jaroslaw Fedevych (UALUG wrote:

>On Wed, Oct 06, 2004 at 04:49:28PM -0000, gboutwel wrote:
>  
>
>>Actually if you use recent snapshots, they include an colinux-debug-daemon,
>>which can be used to capture very detailed debug logs of things.
>> If users could use that daemon to produce logs of situations
>>where latency is a problem and (without inundating the developers)
>>provide them back to us, then we can anaylize them and find more
>>bottlenecks and fix them.
>>
>>    
>>
>
>Ack! Will need to get the time to hunt down what is wrong with it,
>if that recent snapshot will allow me to use bridged networking at all.
>(I'm on a LAN and TAP-Win32 with ICS is not for me)
>
>When I started 20041002 daemon, it was running nice except for the
>winPCAP initialization error (it had found matching network connection,
>but then, all of a sudden, it told ``no matching adapter'' and 
>``Error initializing winpcap''). However, I had no time to investigate
>any deeper, as $BOSSES demanded web server (running on coLinux) here and 
>now :).
>
>  
>