Netdev List
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Sparkletone <sparkletone@gmail.com>
Cc: netdev@vger.kernel.org, shlomif@iglu.org.il
Subject: Re: Fwd: Problem accessing a Certain Remote IP with Kernel 2.6.24-rc1
Date: Sat, 3 Nov 2007 16:38:18 -0700	[thread overview]
Message-ID: <20071103163819.1b038db0@freepuppy.rosehill> (raw)
In-Reply-To: <1855FBA6-5EFE-46E2-A334-AB31C5EDC404@gmail.com>

On Sat, 3 Nov 2007 15:34:18 -0500
Sparkletone <sparkletone@gmail.com> wrote:

> Forwarding this for someone who was getting bounces for some reason.
> 
> Begin forwarded message:
> 
> > From: Shlomi Fish <shlomif@iglu.org.il>
> > Date: November 3, 2007 3:31:56 PM CDT
> > To: sparkletone@gmail.com
> > Subject: Problem accessing a Certain Remote IP with Kernel 2.6.24-rc1
> >
> > Hi all!
> >
> > I hope this mail gets through because last time I checked, I got  
> > bounces
> > whenever I tried to send email to LKML ("not liked source" for mail).
> >
> > I've been having a problem with kernel 2.6.24-rc1 on Mandriva  
> > Cooker. The
> > problem is that after using it for a while connecting through TCP to  
> > the
> > following remote, Internet IP - 212.143.218.31 - takes a very long  
> > time.
> >
> > Here's what I've learned:
> >
> > 1. Kernel 2.6.23 seem to exhibit this problem tooa fter a while.
> >
> > 2. It already happened twice with kernel 2.6.24-rc1.
> >
> > 3. A different computer on the same Home LAN connected via a NAT/ 
> > router has no
> > problem with that IP. (At the same time, the Linux computer exhibits  
> > the
> > problematic behaviour).
> >
> > 4. I could connect using telnet to port 80 eventually, but it took  
> > an awfully
> > long time.
> >
> > 5. I have problem with both HTTP to port 80 and POP.
> >
> > 6. Restarting the network ("/etc/init.d/network restart") does not  
> > help - only
> > a reboot.
> >
> > 7. The network as a whole (Google, etc.) works fine.
> >
> > I need this IP, because it hosts my POP account and my homepage.
> >
> > Per Rik van Riel's advice I prepared Ethereal (libpcap) dumps of the
> > conversations before ("good") and after ("bad") the problem surfaced:
> >
> > http://freehackers.org/~shlomif/files/files/www.sf.org-conn-problem/
> >
> > I'd appreciate if anyone would be able to shed more light on this  
> > problem and
> > hopefully fix it. Please let me know if there's anything else you  
> > need.

Sounds like another instance of the default window scaling causing problems.
Look up TCP window scaling on lwn.net.  There is almost some
stupid middlebox/firewall that doesn't handle window scaling properly.


-- 
Stephen Hemminger <shemminger@linux-foundation.org>

      parent reply	other threads:[~2007-11-03 23:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200711032231.56777.shlomif@iglu.org.il>
2007-11-03 20:34 ` Fwd: Problem accessing a Certain Remote IP with Kernel 2.6.24-rc1 Sparkletone
2007-11-03 23:05   ` David Miller
2007-11-03 23:18     ` Sparkletone
2007-11-03 23:38   ` Stephen Hemminger [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=20071103163819.1b038db0@freepuppy.rosehill \
    --to=shemminger@linux-foundation.org \
    --cc=netdev@vger.kernel.org \
    --cc=shlomif@iglu.org.il \
    --cc=sparkletone@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox