Hi, AFAIK the portrange settings have to be applied identically at the server and the client. You have recompiled the client with the same settings for portrange, correct? Christoph
Dean Pullen schrieb:
Hi all.
I have compiled Amanda using the following options:
./configure --with-user=amanda \
--mandir=/usr/share/man \
--prefix=/usr \
--infodir=/usr/share/info \
--sysconfdir=/etc \
--libdir=/usr/lib \
--libexecdir=/usr/lib/amanda \
--localstatedir=/var/lib \
--with-index-server=admin01 \
--with-gnutar-listdir=/var/lib/amanda/gnutar-lists \
--with-smbclient=/usr/bin/smbclient \
--with-amandahosts \
--with-gnutar=/bin/tar \
--with-group=disk \
--with-owner=amanda \
--with-tape-device=/dev/nst0 \
--with-debugging=/tmp/amanda \
--with-tape-server=admin01 \
--with-configdir=/etc/amanda \
--with-tcpportrange=52000,60000 \
--with-udpportrange=850,851
As you can see, I've ensured the tcp port-range used is between 52000 and 60000.
There are no problems when using amcheck. However, when trying to use amdump, I cannot connect to the client and my firewall reports the following packet drops:
Shorewall:all2all:REJECT:IN= OUT=bond1 SRC=192.168.100.1 DST=192.168.100.20 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=14897 DF PROTO=TCP SPT=55003 DPT=46882 WINDOW=5840 RES=0x00 SYN URGP=0
i.e. packet from Amanda server source port 55003 (within the range I built Amanda with) is trying to be sent to the client on client port 46882 - why is Amanda trying to use this port when I have configured it not to?
Thanks for any replies in advance.
Dean Pullen
