All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Leach <bob@home.com>
To: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: iptables / network / linux issue ...
Date: Thu, 11 Dec 2003 14:32:36 +0200	[thread overview]
Message-ID: <1071145955.22911.9.camel@raylinux.internal> (raw)

Hi

I have a strange network / iptables / Linux problem. I don't know which
it is yet ...

If I ssh to my firewall (which has 4 NIC installed), I then ftp back to
an ftp server on eth2 segment of the firewall and get a whole bunch of
files (about 20 totaling 100MB), I get a transfer rate of 110KB/s
(800Kb/s) - measured on both ends of the connection. This is on a 100Mb
network.

I then ftp from the machine on the internal LAN (eth2) through the
firewall to a machine in the DMZ (eth1 on the firewall). Now I get 1MB/s
- that's more like it.

Any ideas why the first transfer could be so slow?

I have checked my -m limit iptables rules and verified (as can be seen
above) that they are not limiting the packet rate.

Regards

Ray



             reply	other threads:[~2003-12-11 12:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-11 12:32 Ray Leach [this message]
2003-12-14 15:56 ` iptables / network / linux issue Stephen Satchell

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=1071145955.22911.9.camel@raylinux.internal \
    --to=bob@home.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=spoons@rchq.co.za \
    /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.