From: "Nicholas A. Preyss" <nalp@gmx.net>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] l2ping acts like ping
Date: Sat, 17 Apr 2004 15:12:46 +0200 [thread overview]
Message-ID: <20040417131246.GA2461@gmx.net> (raw)
On 0, Marcel Holtmann <marcel@holtmann.org> wrote:
> > we should possibly ping from 0 not 200 like normal ping :)
>
> I don't know why it is from 200, so I applied your patch. Thanks.
snip l2cap.c
...
/* Get next available identificator.
* 1 - 199 are used by kernel.
* 200 - 254 are used by utilities like l2ping,
* etc
*/
...
So probably a ident under 200 could interfere with kernel packets, but
as far as i can see kernel don't enforces using higher ids. So it seems
there is some more digging in the code necessary, to see whether there
is a problem in
Reading the specs it seems that id doesn't matter at all, because it is
intended for an connection oriented ping. And doing some field research,
i found that this modified l2ping works with the stack of my T610 but it
can't ping other bluez stacks, propabably because :
" ... The null identifier (0x0000) is defined as an illegal
identifier and must never be used as a destination end-point. ..."
BT 1.1 spec - page 261
so ident should be at least >= 1.
just my humble opinion
nicholas
p.s. sorry marcel for this dumbass mail copy, just too stupid for my MUA
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2004-04-17 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-17 13:12 Nicholas A. Preyss [this message]
2004-04-18 9:22 ` [Bluez-users] l2ping acts like ping Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-04-17 8:19 Michal Semler (volny.cz)
2004-04-17 9:07 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040417131246.GA2461@gmx.net \
--to=nalp@gmx.net \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.