From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Can't ping remote system
Date: Fri, 13 Sep 2013 11:39:43 -0700 [thread overview]
Message-ID: <CAN0CFw0j1WYBc1GCfirjGvhVo6XQzAWMH7eb3ODMkEe1kZfN-A@mail.gmail.com> (raw)
In-Reply-To: <201309071641.59772.michaelkintzios@gmail.com>
>> > +1 on Alan's hunch. I have not used Squid to comment on the specifics
>> > and also Grant stated that another proxy gave him similar symptoms.
>> > From my limited knowledge a proxy could be stalling because of cache
>> > configuration problems, like running out fs space, or inodes and also
>> > running out of memory if it has to process simultaneous requests from
>> > too many clients at a time. If the problem also manifests when the
>> > clients are within the same subnet, then this is unlikely to be a
>> > network issue.
>>
>> Which hunch was that? I snipped a lot above but I couldn't find it in
>> there.
>
> It was Alan's statement that this problem is not related to your AT&T router.
>
> I have to come back to this. I tried the www.google.com/nexus/ you mentioned
> and noticed that the page eats up 1.3MB to load fully, before it starts
> downloading a flash video. So seems to be a relatively large amount of data
> that brings up this problem and this could point to tcp window scaling.
It also happens on very lightweight sites, but never on
squid-cache.org for some reason.
>> echo 0 > /proc/sys/net/ipv4/tcp_window_scaling
>
> This is typically enabled, but if you notice that a connection stalls and then
> later on it works fine again, it could be related to a firewall/router not
> responding as it should to tcp_window_scaling. In this case disabling this
> would fix the problem when traversing problematic nodes.
>
> If you saw no difference, this suggests that window scaling is not an issue.
I just tested again and 'echo 0 >
/proc/sys/net/ipv4/tcp_window_scaling' on both the client and server
did not fix the stalls.
> I would start with the simplest tests first, which involve isolating suspect
> system components one at a time. Trying to use the same laptop-desktop
> machines within the LAN, takes the router out the equation - full 1500 byte
> MTU will be used by both laptop and desktop.
OK I will try this as soon as I'm back in that location.
Thanks a lot,
Grant
next prev parent reply other threads:[~2013-09-13 18:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 12:28 [gentoo-user] Can't ping remote system Grant
2013-09-01 12:54 ` Michael Hampicke
2013-09-01 12:54 ` Michael Hampicke
2013-09-01 13:28 ` Grant
2013-09-01 14:32 ` Alan McKinnon
2013-09-01 15:04 ` Grant
2013-09-01 16:49 ` Mick
2013-09-01 18:03 ` Grant
2013-09-01 17:50 ` Alan McKinnon
2013-09-01 18:07 ` Grant
2013-09-01 18:32 ` Alan McKinnon
2013-09-01 18:50 ` Grant
2013-09-01 19:10 ` Mick
2013-09-02 18:17 ` Grant
2013-09-02 19:03 ` [gentoo-user] " Nikos Chantziaras
2013-09-05 13:00 ` Grant
2013-09-03 6:12 ` [gentoo-user] " Alan McKinnon
2013-09-03 15:35 ` Mick
2013-09-05 13:17 ` Grant
2013-09-07 15:41 ` Mick
2013-09-13 18:39 ` Grant [this message]
2013-09-05 13:04 ` Grant
2013-09-05 13:09 ` Alan McKinnon
2013-09-05 13:19 ` Grant
2013-09-01 15:03 ` [gentoo-user] " Nikos Chantziaras
2013-09-01 15:09 ` Grant
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=CAN0CFw0j1WYBc1GCfirjGvhVo6XQzAWMH7eb3ODMkEe1kZfN-A@mail.gmail.com \
--to=emailgrant@gmail.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox