Re: How to change default MTU for Obex over L2CAP

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Sathish,

On Tue, Oct 31, 2017 at 9:05 AM, Luiz Augusto von Dentz
<luiz.dentz@xxxxxxxxx> wrote:
> Hi Sathish,
>
> On Tue, Oct 31, 2017 at 5:30 AM, Sathish Narasimman
> <nsathish41@xxxxxxxxx> wrote:
>> Hi,
>>
>> I am trying to do an OPP transfer between 2 Linux bluez system.
>> It is always selecting the 672 MTU size during configuration.
>>
>> May I please know how to change the MTU size.
>
> It looks like for L2CAP we don't set the MTU properly but for RFCOMM we do:
>
> https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/obexd/client/bluetooth.c#n129
>
> I will send a patch in a moment.

Actually, it is the other way around, the RFCOMM don't actually
support setting the MTU since it is a stream, though we should
probably adjust the socket buffer size since we are using 32k for
OBEX.

-- 
Luiz Augusto von Dentz
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux