From: Emil Lenngren <emil.lenngren@gmail.com>
To: "Peter Höller" <drmedvet.hoeller@gmail.com>,
"Bluez mailing list" <linux-bluetooth@vger.kernel.org>
Subject: Re: Instable BLE connection - MTU Request, Attribute not found
Date: Mon, 26 Jul 2021 21:56:11 +0200 [thread overview]
Message-ID: <CAO1O6se1=cHbH=VWyysVFJcumG=aGhquvKDs83CKfhrppzWEBg@mail.gmail.com> (raw)
In-Reply-To: <CAJgPF1LG32ShzPsaPWC64VGRC+odvHYrUYXBiDkTdcZHH78sbQ@mail.gmail.com>
Hi,
Den mån 26 juli 2021 kl 18:19 skrev Peter Höller <drmedvet.hoeller@gmail.com>:
>
> Hi Emil!
>
> Thanks for your input!!
>
> I do have to stabilze this connection, I do not have any other chance,
> unfortunately.
>
> What I fell in my guts right now is that most likely:
> this >>>>
> 2. The peripheral could use white listing to allow connections from
> only specific centrals. In this case the central will always see a
> connection complete immediately followed by a connection failed to be
> established.
> >>>>>
>
> and this>>>>>
> If the peripheral
> responds at least once, but after that at any time it doesn't respond
> to a central's packet within the set supervision timeout, the
> "Connection Timeout" disconnect reason will happen.
> >>>>>
>
> plays a role in my issue!!
>
> However , just to be mentioned, I cannot set (or prolong) supervision
> timeout period, which was my intention initially.
>
> here is what I am able to read/set (sudo nano) under:
> root@odroid:/sys/kernel/debug/bluetooth/hci0#
>
> 6lowpan force_sc_support random_address
> adv_channel_map force_static_address rpa_timeout
> auto_accept_delay hci_revision sc_only_mode
> blacklist hci_version sniff_max_interval
> conn_info_max_age identity sniff_min_interval
> conn_info_min_age identity_resolving_keys ssp_debug_mode
> conn_max_interval idle_timeout static_address
> conn_min_interval inquiry_cache uuids
> dev_class le_auto_conn voice_setting
> discov_interleaved_timeout link_keys white_list
> dut_mode long_term_keys white_list_size
> features manufacturer
>
> Do you have any suggestions for those parameters or am I tuning on the
> wrong place here?
>
> However, I am going for wireshark fur ubuntu now, if I understood you right?
>
> with kind regards
>
> Peter
Someone else should reply to the question about modifying the
supervision timeout. I think BlueZ hardcodes it but I might be wrong.
Either way you could always locate the code for it and recompile with
new parameters.
For a BLE sniffer you could for example use an nRF52 devkit, flash the
sniffer firmware at
https://www.nordicsemi.com/Products/Development-tools/nrf-sniffer-for-bluetooth-le
and then use Wireshark to analyze the traffic in real time.
/Emil
next prev parent reply other threads:[~2021-07-26 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJgPF1JLw40nRXyoXyuGd9hNLWCDeD4ONVM7S_CSE9wQg3gvyA@mail.gmail.com>
2021-07-26 10:56 ` Instable BLE connection - MTU Request, Attribute not found Peter Höller
2021-07-26 15:34 ` Emil Lenngren
[not found] ` <CAJgPF1LG32ShzPsaPWC64VGRC+odvHYrUYXBiDkTdcZHH78sbQ@mail.gmail.com>
2021-07-26 19:56 ` Emil Lenngren [this message]
[not found] ` <CAJgPF1+BJFyryVWzVYGp=qDHjruJWYq-eAHzm+QeR=BGNct+iw@mail.gmail.com>
2021-07-26 20:17 ` Instable BLE connection - MTU Request, Attribute not found - wireshark findings Emil Lenngren
[not found] ` <CAJgPF1KytH81jjezgfOVxrLZzgONqfC4tdTKUy+xPFmP=5f+cw@mail.gmail.com>
2021-10-02 23:57 ` Fwd: " Peter Höller
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='CAO1O6se1=cHbH=VWyysVFJcumG=aGhquvKDs83CKfhrppzWEBg@mail.gmail.com' \
--to=emil.lenngren@gmail.com \
--cc=drmedvet.hoeller@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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.