From: "Nicholas A. Preyss" <nalp@gmx.net>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] MTU and MRU for Bluetooth
Date: Wed, 5 May 2004 23:10:12 +0200 [thread overview]
Message-ID: <20040505211012.GA11210@gmx.net> (raw)
In-Reply-To: <1083692600.4666.57.camel@pegasus>
On 0, Marcel Holtmann <marcel@holtmann.org> wrote:
>> some suggestions for suitable values for MTU / MRU when using pppd and PAP?
>
> are these values not related to the upper protocols like TCP/IP? The
> underlaying RFCOMM protocol is a stream, so you don't have a MTU.
I think, he wants a MTU size that doesn't lead to fragmentation on the
carrying transport medium. I think this doesn't make much sense due to
the "short" packets of bluetooth, and the fact that L2CAP packets can be
up to 2^16 bytes large.
nicholas
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-05-05 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 19:27 [Bluez-users] MTU and MRU for Bluetooth Florian
2004-05-04 17:43 ` Marcel Holtmann
2004-05-05 21:10 ` Nicholas A. Preyss [this message]
2004-05-05 20:50 ` Marcel Holtmann
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=20040505211012.GA11210@gmx.net \
--to=nalp@gmx.net \
--cc=bluez-users@lists.sourceforge.net \
/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.