public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Roland <lroland@gmail.com>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: tg3 in 2.6.12-rc6 and Cisco PIX SMTP fixup
Date: Thu, 16 Jun 2005 14:45:30 +0200	[thread overview]
Message-ID: <4ad99e0505061605452e663a1e@mail.gmail.com> (raw)

Hi

I am testing kernel 2.6.12-rc6 on a 6 IBM 335 servers. The NICs are
gigabit broadcom. If I use the tg3 driver then each of the servers are
unable to communicate with a Cisco PIX  using SMTP fixup, the
connection simply get cut:

-------------
telnet xx.x.xx.xx 25
Trying xx.x.xxx.xx...
Connected to xx.x.xxx.xx.
Escape character is '^]'.
mail to: <test@test.com>
Connection closed by foreign host.
-------------

Using tcpdump does not give me any clue as to what goes wrong, the
connection is simply lost so I am suspecting some kind of TX/RX mess
up. If I instead use the tg3 driver in kernel 2.6.8.1 (or the official
broadcom bcm5700 driver (version 8.1.55) with kernel 2.6.12-rc6) then
I get:

-------------
telnet xx.x.xxx.xx 25
Trying xx.x.xxx.xx...
Connected to xx.x.xxx.xx.
Escape character is '^]'.
220 ***************
mail to: <test@test.com>
250 ok
quit
221 test.com
Connection closed by foreign host.
-------------

So are there any differences in the tg3 driver between 2.6.8.1 and
2.6.12-rc6 that would cause this kind of behaviour ?.

I know that SMTP fixup is mostly a poorly implemented Sendmail
security fix left over from the pre ESMTP era that cripples SMTP
connectivity without offering any real
security advantages. So the best thing would be to turn it off, but
given that I do not control the firewall and the admin refuses to
change it because he believes it to be a security risk then I am
looking for another solution (still hoping that it is not shifting
NICs in all my servers).


Regards.

Lars Roland

             reply	other threads:[~2005-06-16 12:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16 12:45 Lars Roland [this message]
2005-06-16 21:57 ` tg3 in 2.6.12-rc6 and Cisco PIX SMTP fixup 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
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=4ad99e0505061605452e663a1e@mail.gmail.com \
    --to=lroland@gmail.com \
    --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