From owner-freebsd-net Thu Oct 28 8: 2:29 1999 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id EA44C14D46 for ; Thu, 28 Oct 1999 08:02:26 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA91565; Thu, 28 Oct 1999 11:01:08 -0400 (EDT) (envelope-from wollman) Date: Thu, 28 Oct 1999 11:01:08 -0400 (EDT) From: Garrett Wollman Message-Id: <199910281501.LAA91565@khavrinen.lcs.mit.edu> To: Jacopo Pecci Cc: "'FREEBSD'" Subject: TCP threshold In-Reply-To: <2DADC88F8F19D31193340090277A3661017920F7@esegsnt003.erv.ericsson.se> References: <2DADC88F8F19D31193340090277A3661017920F7@esegsnt003.erv.ericsson.se> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > I have just discovered that every time I start a new socket the value of > this variable depends on the final value in the previous socket. It means > that if socket 1 has some drop of packets, the next socket I will establish, > will have a much lover value of the threshold. WHY? each socket is > completely independent from the previous, why it should inherit such > information?. Because you are connecting to the same destination; the conditions in the network are unlikely to vary significantly over the (short) timescale during which the information is cached. You can disable the caching by using the `route' command to set a lock on the ``ssthresh'' route metric for the route(s) in question. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message