public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Nanda Kumar <heramba85@gmail•com>
To: Eric Dumazet <eric.dumazet@gmail•com>
Cc: netdev@vger•kernel.org, davem@davemloft•net
Subject: Re: Default TCP Options creating problems
Date: Fri, 27 Jan 2012 21:21:54 +0530	[thread overview]
Message-ID: <4F22C81A.8090800@gmail.com> (raw)
In-Reply-To: <1327675774.2220.13.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>

Hi Eric,

On Friday 27 January 2012 08:19 PM, Eric Dumazet wrote:
> Le vendredi 27 janvier 2012 à 19:45 +0530, Nanda Kumar a écrit :
>> Hi,
>>
>> I am using Ubuntu 11.10 and unable to connect to my ISP login server.
>> The same is working under windows. Under linux, ISP server does not
>> respond TCP SYN packet even. I did a comparison of packet capture of
>> windows and linux and found, linux include TCP options by default.
>> After manually disabling TCP Timestamp via sysctl, the login is
>> happening fine.
>>
>> Is there any reason why TCP option is enabled by default? The same
>> problem was happening under OpenSUSE 12.1 x86_64 also. My friend
>> informed me that his android mobile is also unable to connect to ISP
>> login server.
> I am very sorry, but you should complain to your ISP, 20 years after RFC
> 1323, it should support it.
>
> TCP options are ... options, and as such should not be denied by a
> conformant TCP stack.
>
>
>
>

Thank you for the reply. Yes even I feel so. I have put up this issue to 
ISP.

However this issue is happening only with TCP timestamp option. All 
other options are working fine. Any idea?

Regards,
Nandakumar

  reply	other threads:[~2012-01-27 15:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F22B17A.2080809@gmail.com>
2012-01-27 14:49 ` Default TCP Options creating problems Eric Dumazet
2012-01-27 15:51   ` Nanda Kumar [this message]
2012-01-27 15:20     ` Eric Dumazet
2012-01-28  2:41       ` NandaKumar

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=4F22C81A.8090800@gmail.com \
    --to=heramba85@gmail$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=eric.dumazet@gmail$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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