The following were executed in a root shell. Receive Side (Device B): $ ./l2test -r 00:02:5B:00:31:21 l2test[29219]: Waiting for connection on psm 4113 ... Transmit Side (Device A): $ ./l2test -s -b 10 00:02:5B:01:FE:DF l2test[29234]: Can't connect: Permission denied (13) $ ./l2test -s -b 10 00:02:5B:01:FE:DF l2test[29311]: Can't connect: Connection refused (111) $ ./l2test -s -b 10 00:02:5B:01:FE:DF l2test[29326]: Can't connect: Connection refused (111) $ ./l2test -s -b 10 00:02:5B:01:FE:DF l2test[29401]: Can't connect: Permission denied (13) $ ./l2test -s -b 10 00:02:5B:01:FE:DF l2test[29478]: Can't connect: Connection refused (111) $ ./l2test -s -b 10 00:02:5B:01:FE:DF l2test[29493]: Can't connect: Connection refused (111) Doesn't appear to work... On Fri, May 13, 2011 at 9:39 AM, Eponymous - <the.epon@xxxxxxxxx> wrote: > What format do you specify the bdaddr in ? > > Cheers. > > On Fri, May 13, 2011 at 9:26 AM, Mika Linnanoja > <mika.linnanoja@xxxxxxxxx> wrote: >> On 05/13/2011 11:13 AM, ext Suraj Sumangala wrote: >>> >>> You have to enable it in the cofigure file and change "test_enable" from >>> "no" to "yes". >>> Edit the file "configure", search for "test_enable" >>> change "test_enable=no" to "test_enable=yes" >>> >>> That is what I do to enable l2test. I guess there could be some other >>> cleaner way to do it. >> >> ./configure --help :) >> >> If you pull from the git repo ./bootstrap-configure already enables most of >> them. >> >> Although lately configure is often *not* complaining if something is missing >> from build dependencies, have to do a bit of trial & error to get it right. >> >> This is very easy to notice when trying to 'make' bluez on a clean system >> where it hasn't ever been built before. >> >> Cheers, >> Mika >> > -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
