Hi, I'm enough. Please get me out of this mailing list, thanks a lot!

From: Mike Mestnik <mmestnik@nagios.com>
Cc: colinux-users@lists.sourceforge.net
Sent: Mon, August 9, 2010 1:21:30 PM
Subject: Re: [coLinux-users] Networking: NSIS installer fails to configure tap correctly.

On 8/9/2010 12:40 PM, Mike Mestnik wrote:
> On 8/6/2010 3:08 PM, Henry Nestler wrote:
>>  Hello Mike,
>> a big difference between pcap-bride and ndis-bride exist inside the
>> code for auto probing name.
>> pcap-bridge: Checks that the interface has an IP address.
>> ndis-bride: Does *not* check IP address. ndis simple use the first
>> network adapter it will find.
>> So, auto probing the name for ndis would fail in mostly all cases.
>> On an other desktop here for me, ndis found a network card, that no
>> longer exist, becaus I have replaced with a new card. :-(
> I gave tap/ndis-bridge another try renaming and specifying both names,
> (tap0/eth0) and this failed.
> It may vary well work on an interface that does not have an IP
> address, it's an interface that does not have link that would be a
> problem.  Given a system with two interfaces makes auto probing a
> possibility, perhaps if there are more interfaces then there are
> interface definitions it should fail.  Also note all the interfaces
> could be setup for DHCP... so getting the interfaces in the correct
> order may not be an issue and it should not be an issue because
> interface probing order is already a known issue.  Perhaps instead of
> a randomly generated address one should be based of the address it's
> bound with, this way udev's persistent code would work as intended and
> there'd be no-more need for the registry saving that's also causing
> problems.
> Given the current status I'm migrating to slirp, though I'd be
> interested in testing solutions to the un-identified problem I'm having.
This is what I have on my local instance that I use day-to-day:

Every thing is fine with this, reboot and it's still all good.  This
makes me think it's a mistake to try and set the name and instead the
real solution is to set a random address.

Mike Mestnik
Technical Team
Nagios Enterprises, INC.
Email:  mmestnik@nagios.com
Web:    www.nagios.com

This SF.net email is sponsored by

Make an app they can't live without
Enter the BlackBerry Developer Challenge
coLinux-users mailing list