Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Marian Stepka <marians@itdimensions.com>
To: netfilter@lists.netfilter.org
Subject: Slow FTP through NAT box...
Date: Fri, 13 Sep 2002 22:07:08 -0400	[thread overview]
Message-ID: <3D8299CC.1CFC740A@itdimensions.com> (raw)

Hi List;

I'm fighthing with NATing issues almost 3 days. Now I'm facing problem,
that It take extremly long to get passive ftp access to the machine
after NAT box. I can access it just using ftp command line client from
Linux machine and none from Win working even PASV mode is enabled. But
anyway initial handshaking take a pretty long, let's say 2 minutes. Box
do nothing else just translate range from priavte IP range to normal
Inet range.

Other services works pretty well as ssh, web. But FTP driving me
slightly mad. Do anybody out there have any idea what I did wrong or
when I can find some info about? Probably I read whole Google. Or I'm
blind or what...

Marian

--
*IN ROOT WE TRUST*
Marian Stepka <mailto:stepka@tris.sk>


             reply	other threads:[~2002-09-14  2:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-14  2:07 Marian Stepka [this message]
2002-09-14  6:52 ` Slow FTP through NAT box Stewart Thompson
2002-09-14 10:47 ` Axel Heinrici

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=3D8299CC.1CFC740A@itdimensions.com \
    --to=marians@itdimensions.com \
    --cc=netfilter@lists.netfilter.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