Re: Phttpget problems (freebsd-update)

2008-06-29 Thread Andrew Storms
Thanks.  I love how I overlooked the simple answer.  I'll give it a try.


On 6/27/08 1:05 PM, Lowell Gilbert
[EMAIL PROTECTED] wrote:

 Andrew Storms [EMAIL PROTECTED] 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/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Phttpget problems (freebsd-update)

2008-06-27 Thread Andrew Storms
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?

Thanks.


---
# sh freebsd-update.sh -f freebsd-update.conf -r 6.3-RELEASE upgrade
Looking up update.FreeBSD.org mirrors... 1 mirrors found.
Fetching metadata signature for 6.2-RELEASE from update1.FreeBSD.org...
done.
Fetching metadata index... done.
Inspecting system... done.

WARNING: This system is running a foobar kernel, which is not a
kernel configuration distributed as part of FreeBSD 6.2-RELEASE.
This kernel will not be updated: you MUST update the kernel manually
before running freebsd-update.sh install.

The following components of FreeBSD seem to be installed:
src/sys world/base world/dict world/doc world/manpages

The following components of FreeBSD do not seem to be installed:
kernel/generic kernel/smp src/base src/bin src/contrib src/crypto
src/etc src/games src/gnu src/include src/krb5 src/lib src/libexec
src/release src/rescue src/sbin src/secure src/share src/tools src/ubin
src/usbin world/catpages world/games world/info world/proflibs

Does this look reasonable (y/n)? y

Fetching metadata signature for 6.3-RELEASE from update1.FreeBSD.org...
done.
Fetching metadata index... done.
Fetching 1 metadata patches. done.
Applying metadata patches... done.
Fetching 1 metadata files... done.
Inspecting system... done.
Fetching files from 6.2-RELEASE for merging... done.
Preparing to download files...
done.
Fetching 6888 patches.102030. done.
Applying patches... done.
Fetching 6748 files... failed.
-

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Phttpget problems (freebsd-update)

2008-06-27 Thread Lowell Gilbert
Andrew Storms [EMAIL PROTECTED] 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/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]