Re: [Bluez-users] l2ping acts like ping

Nicholas A. Preyss
2004-04-17T13:12:46Z

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