Ip_conntrack

I am running amanda server 2.5.2p1 on a Solaris 10 sparc and the remote client is a RH 5.2. On the client I am using the precompiled amanda that comes with RH 5.2.

I was having problem that I narrowed down to the firewall iptables and ports on the RH client.

My iptables file looked like

-A RH-Firewall-1-INPUT -s 128.210.3.177 -m tcp -p tcp --dport 10080 -j ACCEPT
-A RH-Firewall-1-INPUT -s 128.210.3.177 -m udp -p udp --dport 10080 -j ACCEPT
-A RH-Firewall-1-INPUT -s 128.210.4.177 -m tcp -p tcp --dport 10080 -j ACCEPT
-A RH-Firewall-1-INPUT -s 128.210.4.177 -m udp -p udp --dport 10080 -j ACCEPT

and “amcheck –c daily remoteclient” would return ok but when I ran amdump it would get “cannot connect” errors in the dumper. Looking at the dumper log file I tracked down the problem to ports being used by dumper that were not set up in the firewall iptables. To prove this I modified my iptables to the following:

-A RH-Firewall-1-INPUT -s 128.210.3.177 -m tcp -p tcp --dport 10080:60000 -j ACCEPT
-A RH-Firewall-1-INPUT -s 128.210.3.177 -m udp -p udp --dport 10080:60000 -j ACCEPT
-A RH-Firewall-1-INPUT -s 128.210.4.177 -m tcp -p tcp --dport 10080:60000 -j ACCEPT
-A RH-Firewall-1-INPUT -s 128.210.4.177 -m udp -p udp --dport 10080:60000 -j ACCEPT

With this iptables file the backup ran as expected.

In my reading in the zmanda wiki I found information about ip_conntrack_amand and I see what it does but not sure how to set this up. Is ip_conntrack_amanda some module or code and if so where would it be located.

If anyone is using this can you please shead a little more light on how this is used.

Thanks

Robert

--
Robert P. McGraw, Jr.
Manager, Computer System               EMAIL: rmcgraw AT purdue DOT edu
Purdue University                       ROOM: MATH-807
Department of Mathematics              PHONE: (765) 494-6055
150 N. University Street
West Lafayette, IN 47907-2067

Ip_conntrack_amanda