Amanda-Users

Re: Port NNNN not secure (revisited)

2006-07-27 17:32:50
Subject: Re: Port NNNN not secure (revisited)
From: Mike Allen <mallen AT familyradio DOT org>
To: Kevin Till <kevin.till AT zmanda DOT com>
Date: Thu, 27 Jul 2006 14:25:48 -0700
Kevin Till wrote:
Mike Allen wrote:
Kevin Till wrote:

Mike Allen wrote:



try configure with "--with-tcpportrange=50000,50100 --with-udpportrange=512,1023 ..." and recompile.

Open the corresponding ports in the firewall setup.


The reason udp port 34932 was tried because Amanda cannot find a reserved udp port that it can use.



The following occurred while compiling with the values you suggested:
<snip>


Hi,

add "-with-tcpportrange=50000,50100 --with-udpportrange=512,1023" to whatever you have in your configure line. For example:

./configure --with-user=amandabackup --with-group=disk -with-tcpportrange=50000,50100 --with-udpportrange=512,1023


Run configure again and make install.


After configuring both the ta;e server and the client with the suggested portranges above
I got the  following:


14:46:02.501703 IP famrad.familyradio.org.47737 > familyserv.familyradio.org.amanda: UDP, length: 123 14:46:02.543577 IP familyserv.familyradio.org.amanda > famrad.familyradio.org.47737: UDP, length: 50 14:46:02.544603 IP familyserv.familyradio.org.amanda > famrad.familyradio.org.47737: UDP, length: 109 14:46:02.549035 IP famrad.familyradio.org.47737 > familyserv.familyradio.org.amanda: UDP, length: 50


Notice the reference to port 47737 which is outside the range(s) specified. I have a feeling I am doing
something really stupid!

Any help will be greatly appreciated.

Is there a firewall in between? If it's iptables, you can tell by running "iptables -L".

The page below could be helpful too.
http://wiki.zmanda.com/index.php/Configuration_with_iptables


Mike

Kevin:

A properly configured Juniper-Networks firewall made no difference. I have noticed something else that might have a bearing. The version of Amanda-server software is 2.5.0p2 and the client software
is 2.4.5p1. (the latest FreeBSD ports versions).

Could this be the reason for this problem?

Mike