Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

MTU for a peripheral seems incorrect #481

Copy link
Copy link

Description

@AndreiSvatko
Issue body actions

When a client connects to my peripheral, the output of btmon shows that the peripheral's MTU is 517 bytes, and the client's MTU is 512. So the resulting MTU should be 512 bytes. However, SimpleBluez::Characteristic::ValueOptions::mtu in the callback is 517 whenever the client sends something to my characteristic. SimpleBluez::Characteristic::mtu() of any of my characteristics always returns zero. If I split up my message assuming the MTU of 512, everything works fine, while 517 doesn't work.

On a side note: being a peripheral, how can I determine the MTU to initiate an exchange, i.e. there hasn't been anything sent to me by the client, so no callback has been called in which I could see the MTU in ValueOptions?

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.