From owner-freebsd-questions Mon Oct 13 08:52:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA02122 for questions-outgoing; Mon, 13 Oct 1997 08:52:34 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from iris (iris.physics.adelaide.edu.au [129.127.36.47]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA02107 for ; Mon, 13 Oct 1997 08:52:28 -0700 (PDT) (envelope-from kkennawa@iris) Received: by iris; id AA03014; Tue, 14 Oct 1997 01:21:45 +0930 From: Kristian Kennaway Message-Id: <9710131551.AA03014@iris> Subject: Re: install port collection To: wweng@stevens-tech.edu (Wei Weng) Date: Tue, 14 Oct 1997 01:21:45 +0930 (CST) Cc: dwhite@resnet.uoregon.edu, freebsd-questions@FreeBSD.ORG In-Reply-To: from "Wei Weng" at Oct 13, 97 10:05:26 am X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Hi. > I have the same problem. But the things worse here is I am behind a stupid > firewall, so there is no way that i can use ftp to grab the package from > the master site directly. Is there any other way to do it? What type of firewall is it, do you know? If it's SOCKS, you can use the runsocks command to SOCKSify the 'fetch' command which the port install process uses - so it will correctly traverse the firewall (assuming you set up the SOCKS client library properly). This is the setup I have, and it works fine..but other types of firewall are less permissive. If you can use things like rtelnet or rftp to talk to systems on the other side of the firewall, it's likely to be SOCKS. Kris