From: Chris Andrew <candrew@oxspring.com>
To: netfilter@lists.netfilter.org
Cc: peter.marshall@caris.com
Subject: Re: bad ftp speeds through nat
Date: 23 Nov 2004 15:34:18 +0000 [thread overview]
Message-ID: <1101224058.22074.17.camel@candrew.oxspring.com> (raw)
In-Reply-To: <0e8e01c4d0c6$a2725380$49caa8c0@caris.priv>
On Mon, 2004-11-22 at 19:08, Peter Marshall wrote:
> here is the output from the netstat -ni ...
>
> [root@radium root]# netstat -ni
> Kernel Interface table
> Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR
> Flg
> eth0 1500 064374866 0 0 169244643 0 0
> 0 BMRU
> eth0:1 1500 0 698461 0 0 0 674916 0 0
> BMRU
> eth1 1500 067829304 0 0 26760844194 0 0
> 0 BMRU
> eth1:1 1500 0 698461 0 0 0 674916 0 0
> 0 BMRU
> eth2 1500 0 698461 0 0 0 674916 0 0
> 0 BMRU
> lo 16436 0 54 0 0 0 54 0 0
> 0 LRU
>
> and no my firewall is not a P-75 ... :) it is a PIII 850 with 512 MB RAM.
I'm presuming the speeds are poor from your LAN:
Are the transfer speeds OK if you FTP from the firewall?
How do you address the FTP server from your LAN, are you doing any
DNAT/SNAT, or simply routing?
Are transfer speeds always poor from the LAN regardless of which PC
initiates the FTP connection?
What does mii-tool & the above netstat tell you on:
(a) the ftp server
(b) the firewall
(c) LAN workstation
In an attempt to diagnose a failing NIC, try pulling down the speed on
either or both of the NICs on the firewall DMZ interface and FTP server,
using:
mii-tool -F 10baseT-FD eth0
See man mii-tool for available speeds/duplex, etc.
Regards,
Chris
prev parent reply other threads:[~2004-11-23 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 12:56 bad ftp speeds through nat Peter Marshall
2004-11-22 15:04 ` Jason Opperisano
2004-11-22 18:31 ` Peter Marshall
2004-11-22 18:39 ` Peter Marshall
2004-11-22 18:41 ` Jason Opperisano
2004-11-22 19:08 ` Peter Marshall
2004-11-23 15:34 ` Chris Andrew [this message]
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=1101224058.22074.17.camel@candrew.oxspring.com \
--to=candrew@oxspring.com \
--cc=netfilter@lists.netfilter.org \
--cc=peter.marshall@caris.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.