https://devzone.nordicsemi.com/f/nordic-q-a/105368/requesting-an-increase-of-the-mtu-requires-enabling-the-client-roleI am setting up the BLE connection parameters on my project, and using the Lesson 3 of the Bluetooth Low Energy Fundamentals as the basis (while I have experience with BLE, I am new to Nordic). My App is a GATT Server / GAP peripheral (it advertises anden-USTelligent Community 13Wed, 15 Nov 2023 09:51:22 GMThttps://devzone.nordicsemi.com/thread/455723?ContentTypeID=1Wed, 15 Nov 2023 09:51:22 GMT137ad170-7792-4731-bb38-c0d22fbe4515:962ea610-511a-4276-9d3d-8c3a60f204e6jsantosrico<p>Ok, that&#39;s what we&#39;ll do then. Thanks!</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/454228?ContentTypeID=1Mon, 06 Nov 2023 13:52:06 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8ba59454-f870-4496-b2a2-8f13e13ad307Vidar Berg<p>Hello,</p> <p>It&#39;s perfectly fine and not uncommon for a peripheral to support the GATT Client and Server roles at the same time. The CONFIG_BT_GATT_CLIENT setting enables the necessary GATT Client APIs, allowing your peripheral to initiate MTU negotiation. It can also be used for other purposes, such as reading the device name from the connected Central. The only drawback I can&#39;t think of is that <span>CONFIG_BT_GATT_CLIENT=y</span>&nbsp;support will increase your memory footprint somewhat.</p> <p>That said, GAP central devices will usually initiate the MTU negotiation anyway. Additionally, there have been some cases where MTU initiation by the peripheral has led to interoperability issues with older Android phones.</p> <p>Best regards,</p> <p>Vidar</p><div style="clear:both;"></div>