All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raphael Jacquot <raphael.jacquot@imag.fr>
To: dcinege-mlists@psychosis.com
Cc: netfilter@lists.netfilter.org
Subject: Re: Linux forwarding Win XP hosts VERY slowly
Date: Mon, 02 May 2005 09:07:07 +0200	[thread overview]
Message-ID: <4275D19B.7030409@imag.fr> (raw)
In-Reply-To: <200504301341.58023.dcinege-mlists@psychosis.com>

Dave Cinege wrote:
> I've built an advanced rotuign appliance, and I'm having 2 outstanding 
> problems, that I'm being to think are related to the linux ip/netfilter 
> stack, choking on XP traffic (possiblity XP-SP2) hosts that are on the LAN. 
> I'm running 2.4.30 at the moment. 
> 
> The 2 problems I'm seeing:
> 
> 1) Forwarded traffic (most notably web) is VERY slow with XP clients. 

have you tried with a proper web browser, such as firefox ? IE is known
as not respecting the RFC for TCP and sending the HTTP request as data
in the first "SYN" packet (which is only recognised by IIS, of course)
so as to 'make' IE appear faster than it really is..

> Example: Saw this last 2 nights ago: Appliance has a linksys Wifi bridge 
> attached to a NIC. Customer browses through the appliance to the Linksys 
> config page. It moves like molasses. He browse to the local Zope hosted made 
> page. Slow as hell. I unplug his machine, and plug my linux laptop into same 
> switch port. Linksys and Zope pages load adn reload instantly. Plug his 
> machine in....slow again.
> 
> 2) Zope serves user interface pages for the appliance. Zope has been locking 
> solid for no apparent reason, but only when and Windows host is attached. 
> The trick is SOME windows machine don't seem to cause a problem.
> Example: 
> I worked with a unit for 3 days using a customers XP desktop. Not a hiccup. My 
> partner came in and attached to the network and starting connect to our 
> appliance with his XP laptop. Within 15 minutes Zope was hung. 
> 
> I'm really lost. ANY ideas out there?
> 

guess it's one more example of how badly Windows' TCP/IP stack is broken
is so many ways...


  parent reply	other threads:[~2005-05-02  7:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-30 17:41 Linux forwarding Win XP hosts VERY slowly Dave Cinege
2005-04-30 23:06 ` Taylor, Grant
2005-05-01  4:10 ` Alistair Tonner
2005-05-02  7:07 ` Raphael Jacquot [this message]
2005-05-02  7:14   ` Taylor, Grant
  -- strict thread matches above, loose matches on Subject: below --
2005-05-01 12:27 itd.nam
2005-05-02  0:52 Dave Cinege
2005-05-02 17:20 Dave Cinege
2005-05-02 17:50 Dave Cinege
2005-05-02 20:03 ` Taylor, Grant
2005-05-02 20:47 ` Mogens Valentin
2005-05-02 21:29 Dave Cinege

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=4275D19B.7030409@imag.fr \
    --to=raphael.jacquot@imag.fr \
    --cc=dcinege-mlists@psychosis.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.