Re: d-bus or management api for beacon stuff

[Don Zickus <dzickus@redhat.com>]

On Tue, Nov 29, 2016 at 01:28:42PM -0800, Brennan Ashton wrote:
> > > I have had to resort to using the HCI interface to work with
> > > scanning
> > > and advertising beacon packets.  I had mentioned in an earlier
> > > thread
> > > the issue with duplicates.  Not only do you end up with a lot of
> > > spam
> > > on the dbus interface you end up with an ever increasing number of
> > > bluetooth devices.  The Bluetooth mesh uses this transport, so I
> > > really
> > > would like to see a nice interface to support rx/tx of these
> > > packets.
> > 
> > Hi,
> > 
> > Sorry for being ignorant (as I can't quite find the filter duplicate
> > code
> > other than the setting of the bit), but would throttling work
> > here?  Cap the
> > duplicates at say every 100ms or 10x/second.  That probably won't
> > help with
> > power consumption (unless start/stop of the radio is quick?).
> > 
> > Just trying to help move this along..  willing to code/test.
> > 
> > Cheers,
> > Don
> > 
> The thread I mentioned is here:
> https://marc.info/?t=147345134200002&r=1&w=2
> 
> The constant of interest is this LE_SCAN_FILTER_DUP_ENABLE.  I had to
> recompile with this disabled because I never wanted the filter for my
> application.  I had proposed making this an option in the adaptor
> interface, but there did not seem to be any interest.

Hi Brennan,

Yup, I saw that thread earlier and that flag.  I wasn't sure how that flag
was being propagated.  Does it go right to the device?  I guess I thought
the kernel was filtering duplicates, but perhaps not?

Cheers,
Don