--On Monday, December 22, 2003 16:52:25 +0000 Dean Pullen <[EMAIL PROTECTED]> wrote:

> How do I work out which ports the rpm is setup to use?
> Would it be just a default high port?

Look in /tmp/amanda/amandad.*.debug, it should show the configure
command used to build it.  If you don't see
--with-tcpportrange=
--with-udpportrange=
then it is just using it's built-in defaults.  According to PORT.USAGE
it first tries to use ports 512-1023, and if that fails it tries
1024+, for both UDP and TCP.

Frank
> 
> Dean.
> 
> -----Original Message-----
> From: Frank Smith [mailto:[EMAIL PROTECTED] 
> Sent: 22 December 2003 16:45
> To: Dean Pullen; [EMAIL PROTECTED]
> Subject: Re: database01 /export lev 0 FAILED 20031222[could not connect to
> database01]
> 
> --On Monday, December 22, 2003 16:23:29 +0000 Dean Pullen
> <[EMAIL PROTECTED]> wrote:
> 
>> I'm getting a failure when running amdump.
>> database01 /export lev 0 FAILED 20031222[could not connect to database01]
>> 
>> It seems I'm having a few different packets dropped to different ports
> when
>> using amdump, so presumably this is the problem.
>> 
>> What ports does amanda use? I'm seeing ports such as 32776, 32777, 32778
> etc
>> appear in my shorewall packet drop log.
>> 
>> Dean.
>> 
>> 
> Unless you built Amanda to only use a certain port range, the
> data is sent back to random high  ports (the PORT.USAGE file in
> the docs directory of the source has all the details). To run
> Amanda through a firewall, you either need to build it with the
> port range options and allow those ranges through your firewall,
> allow all high ports through your firewall from your clients to
> your server, or use an iptables firewall (the latest versions
> have Amanda support buit in).
>    Which one you choose is based on the security needs of your
> environment.
> 
> Frank

-- 
Frank Smith                                      [EMAIL PROTECTED]
Systems Administrator                           Voice: 512-374-4673
Hoover's Online                                   Fax: 512-374-4501

Reply via email to