[Dibbler] Dibbler under Windows and WPA2 Wireless

[Tomasz Mrugalski]

On Thu, 11 May 2006 somebody known as Stefan Winter wrote:

> problem (at least for the Windows XP port of 0.4.1): when Dibbler is started
> as a system service and the interface is a wireless WPA2 protected network,
> Dibbler will try too early to bind to the interface (after the card
> associated to the Access Point, but before WPA2 authentication completed) and
> will die a horrible death because the interface isn't up yet. How about:
> don't die, instead try every few seconds to bind to the interface...
Hmmm, that doesn't sound like good plan. In 99% cases failing to bind to 
the interface means a big and rather permament problem - wrong interface 
defined, not sufficient rights. So without user's interaction such 
problems won't go away by themself.

But I suppose other possible approach is to introduce new feature, let's 
call it delayed start. There will be a global parameter in the config 
file. which defines (in seconds) how long should Dibbler wait before 
actually getting into action. Of course the default value of this would be 
0, so average user will never notice.

What do you think? Will that do the trick? Is it necessary on relay, 
server and clients? Or on clients only?

> P.S.: You may have seen that I write from Luxembourg - you may want to update
> your Country breakdown of feedback
Great! List has been updated.

-- 
Tomasz Mrugalski,              | "I think there is a world market for     |
thomson(at)klub(dot)com(dot)pl |  about five computers."                  |
                                |     Thomas J. Watson (Chairman, IBM) 1943|