From: James Cameron <james.cameron@hp.com>
To: Dave Henriksen <dhenriksen@optibrand.com>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Ideal mru and mtu ?
Date: Thu, 1 Jul 2004 09:21:27 +1000 [thread overview]
Message-ID: <20040630232127.GK30504@hp.com> (raw)
In-Reply-To: <1088608978.4959.9.camel@linux.site>
An ideal MTU would be the largest that works over the total network path
from the FTP client to the FTP server.
pppd's mru option determines how it negotiates this option with the
peer. The negotiated mru forms the basis for the interface MTU. The
MTU can be changed up and down after interface creation, using "ifconfig
ppp0 mtu".
pppd running over bluetooth just believes it has a byte stream to the
peer. There may be bluetooth specific reasons to choose an MTU that
matches on the air packet sizes, in order to reduce latency, but if your
goal is mainly FTP my guess is that latency isn't important.
--
James Cameron http://quozl.netrek.org/
HP Open Source, Volunteer http://opensource.hp.com/
PPTP Client Project, Release Engineer http://pptpclient.sourceforge.net/
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-06-30 23:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 15:22 [Bluez-devel] Ideal mru and mtu ? Dave Henriksen
2004-06-30 23:21 ` James Cameron [this message]
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=20040630232127.GK30504@hp.com \
--to=james.cameron@hp.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=dhenriksen@optibrand.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox