[Dibbler] Dibbler under Windows and WPA2 Wireless

[Sob]

At 16:13 12.5.2006, you wrote:
>On Fri, 12 May 2006 somebody known as Sob wrote:
> > I have an important correction for above. Only 2k/NT port of Dibbler
> > behaves as described and it's in fact a bug, although a harmless one.
>2k/NT port is one huge mess. Microsoft didn't release asy kind of API for
>those systems, so to get informations about available interfaces or
>add/delete addresses, Dibbler executes ipv6.exe command and parses its
>output.

I completely agree. I just had to point this out, because what I 
wrote previously was based on tests using 2k/NT port which I regulary 
use. It came to my mind later that there can be (and it really is) a 
huge difference between how it works with this port and the XP one.

>Also keep in mind that Microsoft does not support this in any way and
>discourages from using IPv6 on those platforms. Not much hope there...

No more hope is needed here. What is available now is enough. It 
works for testing and sooner or later it won't be needed any more.

But lets forget 2k/NT, this is about something else. The current 
subject are network adapters that can be up, down or even not present 
and Dibbler should handle it better than refusing to start when 
interface is not up.

                                           Sob