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

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

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.

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