<div dir="ltr"><br><br><div class="gmail_quote">On Thu, May 31, 2012 at 2:19 PM, Oleg Goldshmidt <span dir="ltr"><<a href="mailto:pub@goldshmidt.org" target="_blank">pub@goldshmidt.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="im"><br><div class="gmail_quote">On Thu, May 31, 2012 at 2:10 PM, ronys <span dir="ltr"><<a href="mailto:ronys@gmx.net" target="_blank">ronys@gmx.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Looks like Walla's having electric problems at their servers:<div><a href="http://www.globes.co.il/news/article.aspx?did=1000753302" target="_blank">http://www.globes.co.il/news/article.aspx?did=1000753302</a> </div>
<div>
<br></div><br clear="all"></div></blockquote><div> </div></div></div><font face="georgia,serif">FWIW, I get "connection reset" *all the time* from
various Google services - gmail, news, search, maps, youtube. I stopped raising a
brow, just hit the "try again" button. It never occurred to me to
suspect Linux (this looks to me a Google-specific issue) - I thought those were glitches in Google's massive
datacenters... Or maybe in some Israeli cache or whatever.<span class="HOEnZb"><font color="#888888"><br></font></span></font><span class="HOEnZb"><font color="#888888"><br></font></span></div></blockquote><div><br>More likely than a Linux's "fault", is faulty routers (or appliances) on your path to Google's servers, that think they're smarter than Internet endpoints, instead of just... routing traffic, what they were originally supposed to do. Sometimes it's those "smart" QoS boxes...<br>
<br>Recently I did a very long debugging session on a customer of Netvision/Barak, and realized that their equipment doesn't like the "advanced" features enabled by Linux by default - the behavior of the ISP network changed as I modified the things below. I would start echoing 0 to numerous stuff under /proc/sys/net/ipv4/* to see if the problem alleviates.<br>
<br>Start with disabling:<br><br>TCP Timestamps<br>TCP SYN Cookies<br>Window Scaling<br>Selective ACKs (SACKs)<br></div></div><br>Also try MTU @ 1300 for the fun<br><br>And if you have TCP Offloading... might want to disable that, too. It could be your NIC / NIC driver.<br>
<br>Good luck :-)<br><br>-- Shimi<br></div>