On Tue, 2008-08-05 at 17:50 +0200, Velt, R. (Ronald) in 't wrote:

> Thanks for taking the trouble to check this. That, too, is good to know.
> I was merely relaying what I had read here:
> http://madwifi.org/irclogs/%23madwifi.2008-07-17.log
> 
> Some lines from that log:
> 
> 2008-07-17T16:27:16  <Ge0rG> woot. adhoc is broken on ar5007 in the
> new-sam-hal-branch
> 2008-07-17T16:27:26  <Ge0rG> I can receive packets, but sending does not
> work
> .
> 2008-07-17T16:34:45  * Ge0rG badly needs some alternative HAL now :>
> .
> 2008-07-17T16:37:56  <Ge0rG> ok, xmit buffers are not sent out in adhoc
> mode.
> .
> 2008-07-17T16:38:00  <Ge0rG> at least not always.
> .
> 2008-07-17T23:56:13  <Ge0rG> anerion: it worked from time to time, but
> not always :>

I believe it's a different issue.

I can say from my experience that MadWifi has many issues like that, but
they often have a more narrow scope than it seems.  Besides, many such
issues can be worked around, e.g. by using another encryption algorithm
or by doing initialization in a different way.

We should try not to exaggerate the scope of bugs if we don't know it.
It can discourage potential users and even potential contributors.

-- 
Regards,
Pavel Roskin

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/