From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Per-destination MTUs?
Date: Thu, 04 Jul 2002 19:48:55 +0000 [thread overview]
Message-ID: <marc-lartc-102581216109312@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102581144408784@msgid-missing>
On Thu, Jul 04, 2002 at 03:36:28PM -0400, Michael T. Babcock wrote:
> I have some Path-MTU discovery problems it seems; a few sites I deal
> with can only communicate with us if we use an MTU of 1492 (they're on
> ADSL of course ...) and another (in Japan) only works for file transfers
> if we use an MTU of around 1425.
http://lartc.org/HOWTO//cvs/2.4routing/html/lartc.cookbook.mtu-discovery.html
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-07-04 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-04 19:36 [LARTC] Per-destination MTUs? Michael T. Babcock
2002-07-04 19:48 ` bert hubert [this message]
2002-07-04 19:54 ` Michael T. Babcock
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=marc-lartc-102581216109312@msgid-missing \
--to=ahu@ds9a.nl \
--cc=lartc@vger.kernel.org \
/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