On Saturday 29 March 2008, Per-Erik Westerberg wrote:
> fre 2008-03-28 klockan 09:21 +0000 skrev Mick:
> > On Thursday 27 March 2008, Neil Bothwick wrote:
> > > On Thu, 27 Mar 2008 20:33:53 +0200, Uwe Thiem wrote:
> > > > > I'd say, try http.
> > > >
> > > > Jeez. You didn't read the original posting, did you? It's FTP,
> > > > period.
> > >
> > > It's FTP, which is blocked by the firewall, so use only HTTP mirrors
> > > in /etc/make.conf. There is no requirement to use FTP for downloads. If
> > > rsync is also blocked, use emerge-webrsync to update the portage tree
> > > over HTTP.
> > export ftp_proxy=XXX.XX.XXX.XX:80 && emerge -uaDv world, should do what
> > you're after. You can also try export http_proxy of course. It assumes
> > that you know the LAN IP address of your web gateway/firewall at work -
> > i.e. that your work's MSWindows configuration allows plain users to view
> > the MSIE Internet Settings, or your sysadmin will let you know what the
> > address is. If not, boot a LiveCD on a works computer, mount its
> > MSWindows C: drive and search for "proxy". It should lurk somewhere in
> > the registry settings. BartsPE CD will also help you find that, as it can
> > search natively the registry.
> > BTW, if this is anything like my work, then only outbound connections to
> > port 80 are allowed and rsync will not work. Follow the webrsync advice
> > above.
> > HTH.
> You should also set RSYNC_PROXY to "hostname
ort" in order for "emerge
> --sync" to work.
I've tried that and had no success behind my work's firewall, but the OP may