Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Bernhard Rosenkraenzer <bero@linux.cd>
To: Grant Taylor <gtaylor@riverviewtech.net>
Cc: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Weird NAT problem
Date: Sat, 1 Nov 2008 23:59:02 +0100	[thread overview]
Message-ID: <200811012359.02766.bero@linux.cd> (raw)
In-Reply-To: <490CDCC2.3070202@riverviewtech.net>

On Saturday 01 November 2008 23:48:34 Grant Taylor wrote:
> > I've done the same thing the same way before without running into
> > trouble - but this time, clients have no problem keeping an existing
> > transfer going, but initiating connections seems to be troublesome.
>
> Ok...
>
> Is it any connection or just some specific destinations?

It's almost any connection -- and the few connections that do work don't seem 
to be related to the destination. It seems more related to transfer size:

$ scp bero@linux.cd:linux*tar.bz2 .
Password:
linux-2.6.27.2.tar.bz2		0%	0	0.0 KB/s	- stalled -

So, authentication works, and it definitely gets something back or it wouldn't 
know the filename -- but it stops and just sits there as soon as bigger 
amounts of data get transferred.

It can't be a performance problem on the router - this is a quadcore box that 
is (currently) almost idle, and has virtually no traffic on either ethernet 
card.

Regards
Bernhard

  parent reply	other threads:[~2008-11-01 22:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-01 22:07 Weird NAT problem Bernhard Rosenkraenzer
2008-11-01 22:48 ` Grant Taylor
2008-11-01 22:52   ` Grant Taylor
2008-11-01 23:52     ` Bernhard Rosenkraenzer
2008-11-02  0:51       ` Grant Taylor
2008-11-02 11:08     ` Pascal Hambourg
2008-11-02 18:50       ` Grant Taylor
2008-11-01 22:59   ` Bernhard Rosenkraenzer [this message]
2008-11-01 23:14     ` Grant Taylor

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=200811012359.02766.bero@linux.cd \
    --to=bero@linux.cd \
    --cc=gtaylor@riverviewtech.net \
    --cc=netfilter@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