All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: Ricardo Galli <gallir@uib.es>, linux-kernel@vger.kernel.org
Subject: Re: problem with NAT on 2.4
Date: Tue, 20 Nov 2001 16:09:44 -0800	[thread overview]
Message-ID: <20011120160944.B4124@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20011120195443.6842910619@mcrg> <20011120211128.1b9ae5fa.skraw@ithnet.com>
In-Reply-To: <20011120211128.1b9ae5fa.skraw@ithnet.com>

On Tue, Nov 20, 2001 at 09:11:28PM +0100, Stephan von Krawczynski wrote:
> On Tue, 20 Nov 2001 20:54:43 +0100
> Ricardo Galli <gallir@uib.es> wrote:
> 
> > 
> >  > Does anybody have an idea why NAT in 2.4.10 wouldn't work like NAT in some
> >  > cheap dsl-router equipment regarding http-connections?
> >  > Is there any sense in upgrading to 2.4.15-preX?
> >  > I even tried some gateway software based on windoze that is able to NAT - 
> > and
> >  > it works too! I pretty much ran out of ideas...
> > 
> > Did you disable ECN? (echo 0 > /proc/sys/net/ipv4/tcp_ecn)
> 
> Is 0. I didn't explicitely disable, it only happens to be so.
> 
> > Did you try a connection to port 80 from the Linux box?
> 
> Now this is interesting:
> 
> I try a simple telnet www.thedeadman.com 80 (I will post the publicly available
> servers name if you want me to) and this is what happens:
> 
> not working: (connection fails)
> 2.0.39, some 2.2.18, 2.4.10, 2.4.13, some 2.2.19
> 
> working:
> some 2.2.18, some 2.2.19, 2.4.5, 2.4.15-pre3, 2.4.15-pre7

Did you try running tcpdump on the affected server?

  reply	other threads:[~2001-11-21  0:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-20 19:54 problem with NAT on 2.4 Ricardo Galli
2001-11-20 20:11 ` Stephan von Krawczynski
2001-11-21  0:09   ` Mike Fedyk [this message]
2001-11-21 10:17     ` Stephan von Krawczynski
  -- strict thread matches above, loose matches on Subject: below --
2001-11-20 19:41 Stephan von Krawczynski

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=20011120160944.B4124@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=gallir@uib.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skraw@ithnet.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.