This is fixed in CVS. The following patch fixed the problem for me,
but YMMV. In particular, if your firewall is picky about source ports
for outgoing connections, it won't help you. Note that this is *not*
the patch in CVS; OTOH it only affects one file rather than two. It
also brings the behavior of --with-portrange in line with the comments
in the configure file. (With this patch, the --with-portrange option
only affects server ports (that listen for connections), rather than
also affecting client ports (that initiate connections).)
John
--- amanda-2.4.2p2/common-src/stream.c.orig Tue Feb 27 19:53:16 2001
+++ amanda-2.4.2p2/common-src/stream.c Tue Dec 18 15:41:55 2001
@@ -214,10 +214,12 @@
* to get the desired port, and to make sure we return a port that
* is within the range it requires.
*/
+/*
#ifdef PORTRANGE
if (bind_portrange(client_socket, &claddr, PORTRANGE) == 0)
goto out;
#endif
+*/
if (bind_portrange(client_socket, &claddr, 512, IPPORT_RESERVED - 1) == 0)
goto out;
Jason Thomas wrote:
>
> amrecover is broken it does this to me as well, and someone else also
> reported this problem.
>
> just do your recover manually. use 'dd'
>
> On Wed, Mar 06, 2002 at 01:56:58PM +0100, Jordi Vidal wrote:
> > Hi
> > I cant use amrecover, it fails with a port problem:
> >
> > ------------------------------------------------------------------
> > [root@tapeserver /root]# /usr/local/amanda/sbin/amrecover Test-CFG
> > AMRECOVER Version 2.4.2p2. Contacting server on tapeserver ...
> > amrecover: did not get a reserved port: 50059
> > ------------------------------------------------------------------
> >
> > It is the same machine client and server. I compiled amanda with:
> >
> > ./configure --prefix=/usr/local/amanda
> > --with-user=amanda
> > --with-group=disk
> > --with-portrange=50000,50100
> > --with-udpportrange=512,520
> >
> > (BTW: Was udpportrange < 1024 a stupid setting?)
