From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Data sitting and remaining in Send-Q
Date: Mon, 24 Dec 2001 22:58:55 +0100 [thread overview]
Message-ID: <20011224225855.J2461@lug-owl.de> (raw)
In-Reply-To: <20011224211726.H2461@lug-owl.de> <1062462662.1009226676@[195.224.237.69]> <20011224213452.A7761@Marvin.DL8BCU.ampr.org>
In-Reply-To: <20011224213452.A7761@Marvin.DL8BCU.ampr.org>
On Mon, 2001-12-24 21:34:52 +0000, Thorsten Kranzkowski <dl8bcu@dl8bcu.de>
wrote in message <20011224213452.A7761@Marvin.DL8BCU.ampr.org>:
> On Mon, Dec 24, 2001 at 08:44:37PM -0000, Alex Bligh - linux-kernel wrote:
> > If you have an L3 device (router etc.) in the middle, you can get
> > a similar effect if the device does not fragment data correctly
> > (for instance the Cisco into ip tunnels bug - now fixed I think),
> > or, if you are using PMTU discovery (probably), if some evil device,
>
> Jan,
> do you have some DSL Modem in between?
Hi Thorsten!
No, it's not the famous MTU-too-large-and-a-lot-of-fragmentation-needed
problem. It was a broken NIC, unwilling to send frames > ~960 bytes...
MfG, JBG
--
Jan-Benedict Glaw . jbglaw@lug-owl.de . +49-172-7608481
-- New APT-Proxy written in shell script --
http://lug-owl.de/~jbglaw/software/ap2/
next prev parent reply other threads:[~2001-12-24 21:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-24 17:01 Data sitting and remaining in Send-Q Jan-Benedict Glaw
2001-12-24 18:10 ` José Luis Domingo López
2001-12-24 19:00 ` Jan-Benedict Glaw
2001-12-24 19:38 ` Jan-Benedict Glaw
2001-12-24 20:09 ` Mr. James W. Laferriere
2001-12-24 20:17 ` Jan-Benedict Glaw
2001-12-24 20:44 ` Alex Bligh - linux-kernel
2001-12-24 21:34 ` Thorsten Kranzkowski
2001-12-24 21:58 ` Jan-Benedict Glaw [this message]
2001-12-24 21:56 ` Jan-Benedict Glaw
2001-12-25 0:43 ` Alex Bligh - linux-kernel
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=20011224225855.J2461@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-kernel@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