Subject: Re: DLT/bpf questions
To: Iain Hibbert <firstname.lastname@example.org>
From: Greg Troxel <email@example.com>
Date: 10/04/2005 15:46:04
Iain Hibbert <firstname.lastname@example.org> writes:
> There is a problem, in that bluetooth headers are seemingly variable
> length and thus allegedly unsupported - there would be four packet
> types at the HCI interface where I wish to place the tap, with type
> indicated by the leading byte and the relevant packet headers are then
> either 3, 4 or 5 bytes - should I maybe set the header length to 1
So the bluetooth frame arrives and has a type byte first, and then
addresses beyond that? In that case, it feels to me like the header
length is 0 and it's all data. Is this the complete on-the-air frame?
Or is this after some parsing?
Are you going to add this to a bluetooth device driver, or is there
some bluetooth code a la net80211 you are thinking of?
Greg Troxel <email@example.com>