From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Hubert Tonneau <hubert.tonneau@fullpliant.org>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10 TCP troubles
Date: Wed, 05 Jan 2005 14:04:12 +0000 [thread overview]
Message-ID: <1104929316.24187.175.camel@localhost.localdomain> (raw)
In-Reply-To: <0508ECY12@server5.heliogroup.fr>
On Mer, 2005-01-05 at 12:50, Hubert Tonneau wrote:
> troubles (probably lost packets on the Mac side because the Linux machine is
> gigabit connected to the switch, with flow control enabled, and the Mac is
> 100 Mbps connected, full duplex, but without flow control).
Through a firewall ?
next prev parent reply other threads:[~2005-01-05 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 12:50 2.6.10 TCP troubles Hubert Tonneau
2005-01-05 14:04 ` Alan Cox [this message]
2005-01-05 15:41 ` Barry K. Nathan
2005-01-05 18:44 ` Francois Romieu
-- strict thread matches above, loose matches on Subject: below --
2005-01-05 15:30 Hubert Tonneau
2005-01-05 15:14 Hubert Tonneau
2005-01-05 8:13 Hubert Tonneau
2005-01-05 12:07 ` Francois Romieu
2005-01-05 23:33 ` Stephen Hemminger
2005-01-05 23:51 ` Francois Romieu
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=1104929316.24187.175.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=hubert.tonneau@fullpliant.org \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.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 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.