From: Valdis.Kletnieks@vt.edu
To: abonilla@linuxwireless.org
Cc: "'Lars Roland'" <lroland@gmail.com>,
"'Christian Kujau'" <evil@g-house.de>,
"'Linux-Kernel'" <linux-kernel@vger.kernel.org>
Subject: Re: tg3 in 2.6.12-rc6 and Cisco PIX SMTP fixup
Date: Fri, 17 Jun 2005 09:55:49 -0400 [thread overview]
Message-ID: <200506171355.j5HDtogk006607@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 17 Jun 2005 07:33:05 MDT." <001f01c57341$1802c3b0$600cc60a@amer.sykes.com>
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
On Fri, 17 Jun 2005 07:33:05 MDT, Alejandro Bonilla said:
> So what do we really have here? Problem with Cisco or a problem in the
> driver? Both?
Oh - the TCP scaling bits are sent in a TCP Option header - which is what the PIX
is gratuitously throwing out (presumably because they're "optional", given the
sorts of dain bramage we've seen from PIX boxen before. For the longest time,
their 'SMTP Fixup' was anything but....)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2005-06-17 13:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 12:45 tg3 in 2.6.12-rc6 and Cisco PIX SMTP fixup Lars Roland
2005-06-16 21:57 ` Christian Kujau
2005-06-16 21:59 ` David S. Miller
2005-06-16 22:41 ` Jesper Juhl
2005-06-16 22:46 ` David S. Miller
2005-06-16 22:14 ` Lars Roland
2005-06-16 23:54 ` Christian Kujau
2005-06-17 0:05 ` Lars Roland
2005-06-17 0:26 ` Alejandro Bonilla
2005-06-17 1:47 ` Lars Roland
2005-06-17 1:22 ` Alejandro Bonilla
2005-06-17 13:06 ` Valdis.Kletnieks
2005-06-17 13:18 ` Lars Roland
2005-06-17 13:33 ` Alejandro Bonilla
2005-06-17 13:40 ` Lars Roland
2005-06-17 14:03 ` Alejandro Bonilla
2005-06-17 13:52 ` Valdis.Kletnieks
2005-06-17 22:50 ` Lincoln Dale
2005-06-18 5:29 ` Lars Roland
2005-06-18 23:22 ` Alejandro Bonilla
2005-06-19 13:16 ` Lars Roland
2005-06-17 13:55 ` Valdis.Kletnieks [this message]
2005-06-17 4:46 ` Willy Tarreau
2005-06-17 12:45 ` Lars Roland
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=200506171355.j5HDtogk006607@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=abonilla@linuxwireless.org \
--cc=evil@g-house.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lroland@gmail.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;
as well as URLs for NNTP newsgroup(s).