From owner-freebsd-questions@FreeBSD.ORG Sun Jan 20 14:51:19 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6C28AEC0 for ; Sun, 20 Jan 2013 14:51:19 +0000 (UTC) (envelope-from 22karthikreddy@gmail.com) Received: from mail-we0-x22b.google.com (we-in-x022b.1e100.net [IPv6:2a00:1450:400c:c03::22b]) by mx1.freebsd.org (Postfix) with ESMTP id DC8FB748 for ; Sun, 20 Jan 2013 14:51:18 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id u3so1408028wey.16 for ; Sun, 20 Jan 2013 06:51:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=kiQr9F/YqfTD71kPhB5Z7ochvs+O9zQ5TivynZr5rXU=; b=DPN/rcv8Wniq7OWwN8lHbEDQA8Rkhsuo4njAnmIOQp8r9BcwgA40NOzcPzfTHmhtrQ bogiO5O2JYXDWX8d7GE5uO7krjDqacXZDsaJzsokn986YMUIL1wGj6DK8+Go6EnHOQMY LXixSRmJ9kC21b+D6iE6Frz6/xKC6V5lV29oBhIAha7WIdX1MfY4y0Me63P9JEB+g3DZ e8kC4boWdsoKCzBOGfU8Pmwo3l1R/rx0jTecT9aJCtjA6fxcjunlmOwC8pRykWMmBGCe UqnwO+DSwObGLoP90YPGvWC8lyBOB+5zOD4H3uk6hzR+0TTGaOn2Y3WrxBo0yqEv9Xea clFA== X-Received: by 10.180.33.44 with SMTP id o12mr11387958wii.28.1358693478032; Sun, 20 Jan 2013 06:51:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.6.1 with HTTP; Sun, 20 Jan 2013 06:50:57 -0800 (PST) From: Karthik Reddy <22karthikreddy@gmail.com> Date: Sun, 20 Jan 2013 10:50:57 -0400 Message-ID: Subject: What is the timeout of TCP in freeBSD? To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jan 2013 14:51:19 -0000 I was doing a experiment on FreeBSD for testing TCP timeout and RTO. OS is being run from two different VMware versions 4.0 and 5.0. Present Scenario: VMware Player 4.0 I'll start a telnet session to a non-existing system in the network. When I look at the tcpdump the RTO starts at every 3 seconds and after some exponential backoff starts. In this scenario after 75 seconds the TCP gives up and tells me that there is no system existing with the IP and telnet session terminates. Next Scenario: VMware Player 5.0 In this scenario, I did the same but the RTO starts at 5 sec and then varies. In this scenario, it takes more than 120 seconds for telnet session to tell me that there is no system is available in the network. I have seen sysctl in both VM's. net.inet.tcp.keepinit = 75000 Is this problem something related to timing of the VM's or any other issue? -- Karthik Reddy I'm not the best, but I'm not like the Rest