From owner-freebsd-net@FreeBSD.ORG Mon Jan 10 16:59:20 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B95816A4CF for ; Mon, 10 Jan 2005 16:59:20 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8056543D48 for ; Mon, 10 Jan 2005 16:59:19 +0000 (GMT) (envelope-from nocmonkey@gmail.com) Received: by rproxy.gmail.com with SMTP id c16so20482rne for ; Mon, 10 Jan 2005 08:59:18 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=St2E0eI8KshTCLs8ItkEHX3dm4sKDsXNXSM2NAksIzcVRJJoJ5Qr609yGuCXfmnBqgc6O5edfdLRkdvZhF0vAHwh5Xk6KIsbpUebMfIrVUvGs7FZhHHkqbTNY/PMOdNel9eEjoGQaW8WrNjTFrJpItrMVVrcfsIBIDJ0iUo4TV8= Received: by 10.38.90.66 with SMTP id n66mr69124rnb; Mon, 10 Jan 2005 08:59:18 -0800 (PST) Received: by 10.38.22.74 with HTTP; Mon, 10 Jan 2005 08:59:18 -0800 (PST) Message-ID: Date: Mon, 10 Jan 2005 11:59:18 -0500 From: Danny To: Len Conrad In-Reply-To: <6.1.1.1.2.20050110103857.045a9a68@81.255.84.73> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <6.1.1.1.2.20050110103857.045a9a68@81.255.84.73> cc: freebsd-net@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: buildup of Windows time_wait talking to fbsd 4.10 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Danny List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2005 16:59:20 -0000 On Mon, 10 Jan 2005 10:53:39 -0600, Len Conrad wrote: > > We have a windows mailserver that relays its outbound to a fbsd > gateway. We changed to a different fbsd gateway running 4.10. Windows then > began having trouble sending to 4.10. Windows "netstat -an" shows dozens > of lines like this: > > source IP desitination IP > ====================================================================== > TCP 10.1.16.3:1403 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1407 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1415 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1419 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1435 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1462 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1470 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1473 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1478 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1493 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1504 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1507 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1508 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1521 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1526 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1546 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1550 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1568 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1571 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1589 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1592 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1616 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1620 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1629 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1644 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1647 192.168.200.59:25 TIME_WAIT > TCP 10.1.16.3:1654 192.168.200.59:25 TIME_WAIT > > Eventually, the windows SMTP logs line like "cannot connect to remote IP" > or "address already in use" because no local tcp/ip sockets are available, > we think. > > The new gateway/fbsd 4.10 "sockstat -4" shows no corresponding tcp > connections when the Windows server is showing as above. On the fbsd 4.10 > machines, smtp logs, syslog, and dmesg show no errors. > > We switch the windows box to smtp gateway towards the old box/fbsd 4.7, all > is cool. > > Suggestions with how to proceed debugging, please. > > I'm trying to get the dmesg.boot for the 4.7 and 4.10 boxes now, sorry. What shows up when you run a network sniffer on either machines? ...D