From owner-freebsd-net@FreeBSD.ORG Sun Mar 9 09:09:55 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D26B8106566B for ; Sun, 9 Mar 2008 09:09:55 +0000 (UTC) (envelope-from rizzojake@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.188]) by mx1.freebsd.org (Postfix) with ESMTP id 9ED798FC28 for ; Sun, 9 Mar 2008 09:09:55 +0000 (UTC) (envelope-from rizzojake@gmail.com) Received: by rv-out-0910.google.com with SMTP id g13so902218rvb.43 for ; Sun, 09 Mar 2008 01:09:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=3GL0lRuSMKvf9+fGmUAZx6CQXq1KXlnhvrELGHLa8dI=; b=D5WUCkKyeOUmBJkq+RCUOXPB5wBaUGS7/efOPta2AGAGuICWdXxVV3o2aOSgMPLInroA5p2rrD2M3miy8ho2v4/1aseN/I86DNNL8Whn/KvzK83bOTxm9kpiP9IuJCv+6wk4YVzIVI8NmGKqDjm6H2zrtMemmkq6RIoNY9BrHoc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=LYZ2DD+yt65qQ/7GQe19+TCb6MzAK85nqExQypuWFwyfd0xyysfjw0Iy74Y/H59QiS33OGJ6lwfPKA3h6BfHdaXSz/tWSmMnDe/Bb8edz6noCK2AUp+2YjSeNiGVS0Zmem+i8BODNPu2NRpoVCIjJ3xCmaddN4EPaHMVCHpyPzk= Received: by 10.141.113.6 with SMTP id q6mr2327045rvm.135.1205053795182; Sun, 09 Mar 2008 01:09:55 -0800 (PST) Received: by 10.141.22.11 with HTTP; Sun, 9 Mar 2008 01:09:55 -0800 (PST) Message-ID: Date: Sun, 9 Mar 2008 09:09:55 +0000 From: "Jake Rizzo" To: "Mike Silbersack" In-Reply-To: <20080307185203.J27119@niwun.pair.com> MIME-Version: 1.0 References: <20080307185203.J27119@niwun.pair.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: RELENG-7 tcp connectivity problems with certain clients X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Mar 2008 09:09:56 -0000 The patch didn't work, but doing this: sysctl net.inet.tcp.tso=0 sysctl net.inet.tcp.sack.enable=0 Allows the client to connect again. Since my ifconfig doesn't show that my nic supports TSO then I presume it's the sack sysctl that's making it work. The machine's a webserver serving almost exclusively dynamic content - with sack disabled is it likely to affect performance much? Thanks, Jake On Fri, Mar 7, 2008 at 11:52 PM, Mike Silbersack wrote: > > On Fri, 7 Mar 2008, Jake Rizzo wrote: > > > Hi, > > > > I had two 6.3-STABLE boxen which have been happily running away for > months > > on end now without any problems. Last week I upgraded (via buildworld) > both > > boxes to 7.0-STABLE. Since then I've had reports of some clients being > > unable to connect via tcp. I've seen this happen first hand on an > affected > > remote machine. Traceroute & ping gets to the machine just fine > > but connecting to an open tcp port on the machine just times out. The > > remote box was a XP machine and so I didn't have the luxury of tcp dump > on > > that end, however I did get a chance to run it at the freebsd end: > > Try this change; it was too late to be put in 7.0, but it will be merged > to 7-stable in a few days: > > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_var.h.diff?r1=1.160;r2=1.161 > > -Mike >