From: Ken Price <kprice@agentware.net>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] MTU problem with simple router?
Date: Fri, 25 Oct 2002 16:53:30 +0000 [thread overview]
Message-ID: <marc-lartc-103556487626277@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103556037120636@msgid-missing>
All of our public IPs are reverse mapped. The initial connection to the
site is fast. The delay happens when data starts comming back. A way to
visualize this problem is using a browser. You hit "Go" and the target site
immediately returns text, but like a low-bandwidth or overloaded site,
graphics trickle back. This problem is not limited to a single site ...
it's all of them. And isn't limited to a single router, I have two
different production evironments setup with different loadbalancer/firewall
combos. What they both have in common is the RedHat router doing simple
forwarding. One in each environments.
-Ken
>> Any suggestions on where to go with this?
>If I have a tcp delay, I always check the dns config. In many cases, there
is
>no reverse dns lookup of the ip-address so the other hosts waits for the
>dns-timeout before allowing the connection. So, has your ip-address a
>reverse dns entry?
>Stef
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-10-25 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 15:38 [LARTC] MTU problem with simple router? Ken Price
2002-10-25 16:32 ` Stef Coene
2002-10-25 16:53 ` Ken Price [this message]
2002-10-25 17:22 ` Stef Coene
2002-10-25 18:26 ` Ken Price
2002-10-25 21:10 ` Ken Price
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=marc-lartc-103556487626277@msgid-missing \
--to=kprice@agentware.net \
--cc=lartc@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 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.