carrano at ricardocarrano.com
Fri Feb 8 05:42:02 EST 2008
This script is meant to test infra-structure association, so I believe it
can only indirectly help with #6287 (mesh association). But of course we can
always make a new one for the mesh forming and for the school server
I should comment this (and I will) on the ticket, but I believe #4975 is not
present in recent builds. At least in my tests, the association happens at
the first attempt (or it won't happen at all because of any other transient
issue, like WEP or WPA support).
On Feb 7, 2008 9:29 PM, John Watlington <wad at laptop.org> wrote:
> I don't know the answer to your question. But the test you've proposed
> would help figure out #6287 and #4975. In my case, it may be problems
> associating with a new mesh after suspending, or after 24+ hours.
> We eagerly anticipate it.
> On Feb 7, 2008, at 4:21 PM, Ricardo Carrano wrote:
> > As part of the wireless test suite, I am writing a test script for
> > the association process. Basically you write a configuration file
> > with the info on some essids; the script parses the file and tries
> > to associate to each of the APs in loop.
> > The only drawback is that the script kills NetworkManager, so it
> > does not test all the components involved (only firmware and driver).
> > I suspect it is possible to send dbus-messages to NM asking for it
> > to associate, and then listen to the bus and wait for an answer.
> > My question is whether this mechanism is documented somewhere.
> > Comments in the idea are also welcome, of course.
> > Any help you be appreciated. Thanks!
> > --
> > Ricardo Carrano
> > _______________________________________________
> > Devel mailing list
> > Devel at lists.laptop.org
> > http://lists.laptop.org/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Devel