From: Rudi Starcevic <tech@wildcash.com>
To: "netfilter@lists.netfilter.org" <netfilter@lists.netfilter.org>
Subject: Re: Port-forwarding Perfomance
Date: Thu, 24 Feb 2005 08:09:09 -0800 [thread overview]
Message-ID: <421DFC25.5010000@wildcash.com> (raw)
In-Reply-To: <20050223211053.GA12107@bender.817west.com>
Hi,
>1 - you have a speed/duplexing mismatch between the internal interface
>of the firewall and your internal switch...or the windows box and the
>internal switch (but you should notice that slowing internal
>transfers)...or both.
>
>
Thanks, am checking on this one now ..
>2 - your internet connection is ppp/pppoe and you have an MTU problem.
>since the linux gateway is directly connected, it knows to lower the MTU
>of the external interface, but machines behind it would continue to
>assume an MTU of 1500; and in the absence of functioning PMTU
>discovery, would suffer from significant packet loss due to the need for
>fragmentation.
>
>
This is on a 100MB link at choopa .com.
The windows machine being forward to is on a Gigabit network.
>3 - you're using some traffic shaping script (like the wondershaper) and
>it is misconfigured.
>
>
Only using Iptables.
Thanks for these leads, am following up now.
Cheers
Rudi
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 22/02/2005
next prev parent reply other threads:[~2005-02-24 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 1:33 Port-forwarding Perfomance Rudi Starcevic
2005-02-23 10:56 ` Jose Maria Lopez Hernandez
2005-02-24 14:29 ` Rudi Starcevic
2005-02-23 20:56 ` Maxime Ducharme
2005-02-23 21:10 ` Jason Opperisano
2005-02-24 16:09 ` Rudi Starcevic [this message]
2005-02-24 0:07 ` R. DuFresne
2005-02-25 0:15 ` Rudi Starcevic
2005-02-24 12:53 ` Daniel
2005-03-08 11:12 ` Andy Furniss
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=421DFC25.5010000@wildcash.com \
--to=tech@wildcash.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 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.