From: Jerry A! <jerry@thehutt.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Re: Problems with initial gentoo rc5 binary inst all - GRUB
Date: Wed Jul 18 16:46:01 2001 [thread overview]
Message-ID: <20010718184602.A3601@gemini.thehutt.org> (raw)
In-Reply-To: <411301487662D411ADDB0090274F3A7502260AF6@uswaumsx01medge.med.ge.com>; from Darren.Greer@med.ge.com on Wed, Jul 18, 2001 at 04:48:35PM -0500
On Wed, Jul 18, 2001 at 04:48:35PM -0500, Greer, Darren (MED) wrote:
: Yah, this rsync issue seems like it may be a pain. With Debian I could
: easily apt-get update using the proxy. However, when I set the proxy in
: make.globals or using the env rsync_proxy it still does not work. If I
: strace it I get:
:
: Here is proof that I can get out via port 80 from the shell
: #######################
: flash /root > export http_proxy=http://3.231.200.25:80
: flash /root > export rsync_proxy=3.231.200.25:80
: flash /root > export http_proxy=3.231.200.25
: flash /root > wget http://gentoo.org
I think I see some of your problems. First, RSYNC_PROXY (and since it's
in the environment it's all caps) only specifies a rsync server to proxy
with. However, rsync_proxy connections only work on port 873.
Otherwise, rsync will use rsh/ssh to grab it's data. Now both of those
work on port 22.
It just dawned on me that in a previous e-mail you mentioned that you
only had ports 21 and 80 open. Well, there's your problem--you only
have ftp and http open on your firewall. You'll need to either open up
port 22 (ssh/rsh) or put in some stateful rules to keep an outgoing
connection open.
Hope this helps...
--Jerry
name: Jerry Alexandratos || Open-Source software isn't a
phone: 703.599.6023 || matter of life or death...
email: jerry@thehutt.org || ...It's much more important
|| than that!
next prev parent reply other threads:[~2001-07-18 22:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 15:49 [gentoo-dev] Re: Problems with initial gentoo rc5 binary inst all - GRUB Greer, Darren (MED)
2001-07-18 16:46 ` Jerry A! [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-19 9:36 Greer, Darren (MED)
2001-07-19 6:44 Greer, Darren (MED)
2001-07-19 8:40 ` Daniel Robbins
2001-07-18 15:37 Grant Goodyear
2001-07-18 14:48 Greer, Darren (MED)
2001-07-18 14:44 Grant Goodyear
2001-07-18 13:50 Greer, Darren (MED)
2001-07-18 13:25 Grant Goodyear
2001-07-18 12:33 Greer, Darren (MED)
2001-07-18 12:16 Greer, Darren (MED)
2001-07-18 12:23 ` Daniel Robbins
2001-07-18 11:40 Greer, Darren (MED)
2001-07-18 11:54 ` Daniel Robbins
2001-07-18 11:39 Greer, Darren (MED)
2001-07-18 11:57 ` Daniel Robbins
2001-07-18 10:02 Greer, Darren (MED)
2001-07-18 11:33 ` Daniel Robbins
2001-07-18 9:00 Greer, Darren (MED)
2001-07-18 11:26 ` Daniel Robbins
2001-07-18 7:16 Greer, Darren (MED)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010718184602.A3601@gemini.thehutt.org \
--to=jerry@thehutt.org \
--cc=gentoo-dev@cvs.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox