From: Dave Henriksen <dhenriksen@optibrand.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Ideal mru and mtu ?
Date: Wed, 30 Jun 2004 08:22:58 -0700 [thread overview]
Message-ID: <1088608978.4959.9.camel@linux.site> (raw)
Hi,
I was wondering if anyone had an idea as to what would be an ideal mru
and mtu for me to specify when using pppd over a bluetooth connection.
I am connecting to an access point that typically is quite busy, and has
two simultaneous connections (ppp clients) connected to it, mainly for
ftp transfer of files with an average size of 30K.
Any ideas ?
Thanks,
Dave
-------------------------------------------------------
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
next reply other threads:[~2004-06-30 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 15:22 Dave Henriksen [this message]
2004-06-30 23:21 ` [Bluez-devel] Ideal mru and mtu ? James Cameron
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=1088608978.4959.9.camel@linux.site \
--to=dhenriksen@optibrand.com \
--cc=bluez-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox