From owner-freebsd-questions@FreeBSD.ORG Mon Jun 30 02:12:07 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AEABB1065670 for ; Mon, 30 Jun 2008 02:12:07 +0000 (UTC) (envelope-from astorms@ncircle.com) Received: from mail.ncircle.com (mail.ncircle.com [64.84.9.150]) by mx1.freebsd.org (Postfix) with ESMTP id 95CC18FC0C for ; Mon, 30 Jun 2008 02:12:07 +0000 (UTC) (envelope-from astorms@ncircle.com) Received: from CORP-MAIL.ad.ncircle.com (corpmail-01.ncircle.com [192.168.75.90]) by mail.ncircle.com (8.14.2/8.14.2) with ESMTP id m5U2C1B0009354 for ; Sun, 29 Jun 2008 19:12:01 -0700 (PDT) (envelope-from astorms@ncircle.com) Received: from 192.168.5.202 ([192.168.5.202]) by CORP-MAIL.ad.ncircle.com ([192.168.75.94]) via Exchange Front-End Server webmail-01.ad.ncircle.com ([192.168.75.93]) with Microsoft Exchange Server HTTP-DAV ; Mon, 30 Jun 2008 02:12:02 +0000 User-Agent: Microsoft-Entourage/11.4.0.080122 Date: Sun, 29 Jun 2008 19:12:00 -0700 From: Andrew Storms To: Message-ID: Thread-Topic: Phttpget problems (freebsd-update) Thread-Index: AcjYkSy/h0vdT+uATtqPlvc8SnihKABxYEu0 In-Reply-To: <44ej6iprsk.fsf@be-well.ilk.org> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Score: -4.294 () ALL_TRUSTED,AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 64.84.9.150 Subject: Re: Phttpget problems (freebsd-update) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 02:12:07 -0000 Thanks. I love how I overlooked the simple answer. I'll give it a try. On 6/27/08 1:05 PM, "Lowell Gilbert" wrote: > Andrew Storms writes: > >> Anyone else experiencing issues related to phttpget when using >> freebsd-update? What I'm finding is that there is just enough delay between >> retrieval of the 6.2 and the 6.3 patches; that the upstream firewall closes >> the NAT. Then phttpget attempts to retrieve the 6.3 patch set and just >> assumes the session is already open. Firewall sends a RST back and phttpget >> doesn't attempt a new 3-way handshake. The end result is freebsd-update >> then just gives up. >> >> If it helps at all, I'm so far only seeing this happen behind a Cisco ASA >> appliance. >> >> Anybody else seen this and/or have a suggested work around? > > Maybe perform the 6.2 update and the 6.3 update in separate operations? > > -- > Lowell Gilbert, embedded/networking software engineer, Boston area > http://be-well.ilk.org/~lowell/