From owner-freebsd-bluetooth@FreeBSD.ORG Fri Nov 12 15:18:52 2010 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC009106564A for ; Fri, 12 Nov 2010 15:18:51 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 909448FC19 for ; Fri, 12 Nov 2010 15:18:51 +0000 (UTC) Received: by yxs7 with SMTP id 7so496224yxs.13 for ; Fri, 12 Nov 2010 07:18:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=/je33dz3dYG495csB89h7kIlL05FV4cnja3pm86YneU=; b=QQ9M57OiEzWBHgbBn95dHvKKkgTGlkJ1AKdbbSaUq2SlIxqvYG5+ZhNpj2UJHWcrEm N8WOCQ4H/26lcPNonnn4LIaW1oxwpJozsa+LF3L5AC/j8fjTTowq7kklEBkleiZsrzGN jUFhMzszsVoWoNetLHBc4c3599SV/2zqe4Ytg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ZebcFth9333FEja4powgPMFpxN2PzFaIIzDp3Y5+yEJRh2ThrMX2jmhinF+ybjRwS1 QjNyupmiAKiEyvcxVkyqvmm1wexyAf7qSw+p4UE52MdKHgN4adzX0l63RyggTzvoVrTl 9WP0QW1d3bO1IXmZ3nKlYhQngq6rIcvWIh1+I= MIME-Version: 1.0 Received: by 10.42.22.79 with SMTP id n15mr2182660icb.183.1289575126263; Fri, 12 Nov 2010 07:18:46 -0800 (PST) Received: by 10.231.207.14 with HTTP; Fri, 12 Nov 2010 07:18:46 -0800 (PST) In-Reply-To: <20101112070051.GA48569@amp2.iem.pw.edu.pl> References: <64FA2044DA694411995A309FF342396C@marekdesktop> <20101112050506.GA18796@amp2.iem.pw.edu.pl> <20101112062852.GA39843@amp2.iem.pw.edu.pl> <20101112064459.GA45107@amp2.iem.pw.edu.pl> <20101112070051.GA48569@amp2.iem.pw.edu.pl> Date: Fri, 12 Nov 2010 07:18:46 -0800 Message-ID: From: Maksim Yevmenkin To: Andrzej Tobola Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Fri, 12 Nov 2010 16:43:52 +0000 Cc: Subject: Re: l2ping - strange seq_no X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Nov 2010 15:18:52 -0000 Andrzej, > The last question - is it OK that seq_no has strange values or jumps: > > z2% l2ping -a FF1 > 4 bytes from FF1 seq_no=1633905441 time=798.277 ms result=0 > 4 bytes from FF1 seq_no=1633905441 time=13.756 ms result=0 > 4 bytes from FF1 seq_no=1633905441 time=28.755 ms result=0 > 4 bytes from FF1 seq_no=1633905441 time=25.755 ms result=0 > 4 bytes from FF1 seq_no=1633905441 time=28.761 ms result=0 > 4 bytes from FF1 seq_no=1633905441 time=32.018 ms result=0 > ^C > z2% l2ping -a FF2 > 0 bytes from FF2 seq_no=0 time=37.552 ms result=0x9 > 0 bytes from FF2 seq_no=1 time=5.754 ms result=0x9 > 0 bytes from FF2 seq_no=2 time=5.756 ms result=0x9 > 4 bytes from FF2 seq_no=1633905441 time=107.755 ms result=0 > 4 bytes from FF2 seq_no=1633905441 time=30.758 ms result=0 > 4 bytes from FF2 seq_no=1633905441 time=25.759 ms result=0 > 4 bytes from FF2 seq_no=1633905441 time=27.757 ms result=0 > 4 bytes from FF2 seq_no=1633905441 time=25.754 ms result=0 > 4 bytes from FF2 seq_no=1633905441 time=93.766 ms result=0 > 4 bytes from FF2 seq_no=1633905441 time=65.763 ms result=0 > 4 bytes from FF2 seq_no=1633905441 time=87.759 ms result=0 > 4 bytes from FF2 seq_no=1633905441 time=24.758 ms result=0 > ^C > z2% l2ping -a VV1 > 44 bytes from VV1 seq_no=0 time=3887.731 ms result=0 > 44 bytes from VV1 seq_no=1 time=21.762 ms result=0 > 44 bytes from VV1 seq_no=2 time=27.014 ms result=0 > 44 bytes from VV1 seq_no=3 time=9.761 ms result=0 > 44 bytes from VV1 seq_no=4 time=47.760 ms result=0 > 44 bytes from VV1 seq_no=5 time=14.017 ms result=0 > 44 bytes from VV1 seq_no=6 time=16.852 ms result=0 > 44 bytes from VV1 seq_no=7 time=27.762 ms result=0 > 44 bytes from VV1 seq_no=8 time=53.765 ms result=0 > 44 bytes from VV1 seq_no=9 time=31.762 ms result=0 > 44 bytes from VV1 seq_no=10 time=13.765 ms result=0 > 44 bytes from VV1 seq_no=11 time=34.762 ms result=0 > > or it signals some memory corruption ? not necessarily. l2cap does not have sequence numbers in protocol headers (like ip/icmp does), so l2cap(8) fakes sequence numbers by putting them into l2cap echo request packet payload. some devices return original payload in l2cap echo response thus making it easy to get sequence numbers back. some devices do not return any payload back (i.e. l2cap(8) will not get any sequence numbers back). in your case, payload is returned, but it appears to be different (constant?). what kind are FF1 and FF2 devices? could you please install hcidump utility from ports (i think its under net/comm) and get a trace to see what payload is being sent out and what payload is received back? thanks, max