Re: [Bluez-devel] L2CAP: One failing connection hurts others?

[Marcel Holtmann <marcel@holtmann.org>]

Hi Stefan,

> Hmmm, these timeouts are really difficult. I've written a script 
> "l2client.sh" (see below) using bluez-utils' l2test to make sure the 
> problem is not inside of my code. I also included the output of a 
> testrun. Take a look at it!
> 
> #### BEGIN SCRIPT l2client.sh ####
> 
> #!/bin/bash
> 
> ROUNDS=10
> SLEEP=`which sleep`
> TSLEEP=5
> SERVER1="00:02:72:B1:1D:6C"
> SERVER2="00:02:72:B1:1D:62"
> 
> for i in `seq 1 $ROUNDS`;
> do
>         printf "Round $i of $ROUNDS\n"
> 
>         printf "Connecting to Server $SERVER1...\n"
>         l2test -s -N 1 $SERVER1
>         printf "\n"
> 
>         printf "Connecting to Server $SERVER2...\n"
>         l2test -s -N 1 $SERVER2 &
>         printf "Waiting for $TSLEEP seconds...\n"
>         $SLEEP ${TSLEEP}s
>         printf "\n"
> done
> 
> printf "l2client.sh terminating.\n"
> 
> #### END SCRIPT l2client.sh ####

use the linger support of the L2CAP socket and put a "sleep 2" between
the first and the second l2test call.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel