public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Roland <lroland@gmail.com>
To: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
Cc: Alejandro Bonilla <abonilla@linuxwireless.org>,
	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 15:18:03 +0200	[thread overview]
Message-ID: <4ad99e05050617061864f286a2@mail.gmail.com> (raw)
In-Reply-To: <200506171306.j5HD6E01001899@turing-police.cc.vt.edu>

On 6/17/05, Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
> On Fri, 17 Jun 2005 03:47:00 +0200, Lars Roland said:
> > \b
> >
> > On 6/17/05, Alejandro Bonilla <abonilla@linuxwireless.org> wrote:
> > > one question,
> > >
> > >     Can I know what is the problem?
> > >:I have 2 tg3 adapters, lots e100's and some Cisco PIX and devices.
> > >
> > > I can try to reproduce it and see if anyone has something to say about it.
> >
> > Yes please. As I see it. Enable smtp fixup protocol on your cisco pix
> > (you will need to have a smtp server to point it to), then on some
> > linux system running with a kernel greater than 2.6.8.1 do a telnet to
> > the smtp server that is firewalled and try to issue a smtp command.
> >
> > Note that cisco has a bug report on smtp fixup banner hiding issues in
> > cisco os 6.3.4 but it should not result in the connection getting
> > dropped, it also does not explain why this problem does not seam to
> > exists on kernels prior to 2.6.9.
> 
> 2.6.9? This rings a bell.. ;)
> 
> Does disabling TCP window scaling fix it?
> 
> echo 0 > /proc/sys/net/ipv4/tcp_window_scaling

Yes it does solve it. 

Thanks so much - this will be much easier than getting the largest ISP
in Denmark to update there Cisco to a new version.


Regards.

Lars Roland

  reply	other threads:[~2005-06-17 13:20 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 [this message]
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=4ad99e05050617061864f286a2@mail.gmail.com \
    --to=lroland@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=abonilla@linuxwireless.org \
    --cc=evil@g-house.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