emerge-webrsync should work fine over port 80.  Can't you configure the
firewall to accept this port.  You could also write a script that opens the
port calls emerge-webrsync and then locks it back down if you don't want
that port open.  Another safe way to do it is to run it through a proxy
server.  I'm not sure if this is the best way but certainly should work.

On 2/24/06, Rick van Hattem <Rick.van.Hattem@fawo.nl> wrote:
>
> On Monday 13 February 2006 19:40, Daniel da Veiga wrote:
> > I have this server at work, it has been running ok for a long time,
> > but I'd like to install some new apps to it, but I have a strongly
> > configured firewall (no rsync) and emerge-webrsync seems to fail every
> > time.
> >
> > Is there another way to update portage tree? For my first update I
> > downloaded the snapshot and decompressed it directly to the filesystem
> > (but that requires a reboot and its kinda "brute force"). Is there a
> > way to download the snapshot and make emerge or even emerge-webrsync
> > to use the downloaded file instead of trying to download a new one?
> >
> > Thanks for any sugestion.
> >
> > --
> > Daniel da Veiga
> > Computer Operator - RS - Brazil
> > -----BEGIN GEEK CODE BLOCK-----
> > Version: 3.1
> > GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
> > PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
> > ------END GEEK CODE BLOCK------
> And it isn't possible to enter the proxy data for emerge-webrsync (if
> there is
> any)
>
> Btw, just packing /usr/portage from another system and unpacking it again
> shouldn't need a reboot, after unpacking it should be able to run.
>
> --
> Rick van Hattem Rick.van.Hattem(at)Fawo.nl
>
>
>