The TSecr value/field in the return packet from google is wrong, it should be identical to the timestamp you sent and it is not.
2013/1/24 shimi <linux...@shimi.net> > > > On Thu, Jan 24, 2013 at 8:54 AM, Shachar Shemesh <shac...@shemesh.biz>wrote: > >> Hail the conquering hero! >> >> Color me dumbfounded. Disabling TCP timestamps actually allows me to >> connect to Google. Reenabling them re-introduces the problem. >> >> The only question still remaining is "why"? I have up on the site two >> captures. One of the working session, and one of the not working session. >> To me, this still looks like a kernel bug. >> >> Get them: >> http://www.shemesh.biz/connection/working.dump >> http://www.shemesh.biz/connection/notworking.dump >> >> Ideas, anyone? >> > > Really have to go now, so I cannot take a look at the captures, but... > > You started the thread with "This is NOT an ISP problem". Any chance > you're using BezeqInt? > > -- Shimi > > _______________________________________________ > Linux-il mailing list > Linux-il@cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > >
_______________________________________________ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
