Hello,

We are experiencing problems when trying to backup a Linux Suse 9.1 
machine with software iptables. That machine is a firewall, and it's 
used to protect and NAT (network address translation) an almost hundred 
client machines. Legato client and server are 7.1.2.

Because of this NAT feature, firewall external interface looks like this:

eth0.2    Link encap:Ethernet  HWaddr 00:D0:B7:B2:B8:1C
           inet addr:192.168.51.54  Bcast:192.168.51.255  Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1496  Metric:1
           RX packets:20671245 errors:0 dropped:0 overruns:0 frame:0
           TX packets:154132767 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:1456142824 (1388.6 Mb)  TX bytes:1857892331 (1771.8 Mb)

eth0.2:FW Link encap:Ethernet  HWaddr 00:D0:B7:B2:B8:1C
           inet addr:192.168.51.49  Bcast:192.168.51.255  Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1496  Metric:1

eth0.40   Link encap:Ethernet  HWaddr 00:D0:B7:B2:B8:1C
           inet addr:192.168.69.11  Bcast:192.168.69.255  Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1496  Metric:1
           RX packets:83552983 errors:0 dropped:0 overruns:0 frame:0
           TX packets:35446 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:913542860 (871.2 Mb)  TX bytes:1630516 (1.5 Mb)

eth0.40:F Link encap:Ethernet  HWaddr 00:D0:B7:B2:B8:1C
           inet addr:192.168.69.179  Bcast:192.168.69.255
Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1496  Metric:1

eth0.40:F Link encap:Ethernet  HWaddr 00:D0:B7:B2:B8:1C
           inet addr:192.168.69.180  Bcast:192.168.69.255
Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1496  Metric:1

eth0.40:F Link encap:Ethernet  HWaddr 00:D0:B7:B2:B8:1C
           inet addr:192.168.69.181  Bcast:192.168.69.255
Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1496  Metric:1

eth0.40:F Link encap:Ethernet  HWaddr 00:D0:B7:B2:B8:1C
           inet addr:192.168.69.182  Bcast:192.168.69.255
Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1496  Metric:1

eth0.40:F Link encap:Ethernet  HWaddr 00:D0:B7:B2:B8:1C
           inet addr:192.168.69.183  Bcast:192.168.69.255
Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1496  Metric:1

.............. (There is a virtual interface for ever IP address to 
NAT)..........................

The problem with backup software is that legato is trying to resolve
every IP address that is declared on firewall external interface, and 
sometimes this can cause timeouts problems.

I don't understand why legato software can't use only 192.168.51.54 
(firewall IP address)? this IP is well defined in /etc/hosts as in DNS 
while NAT IPs are variable and not always well configured at DNS. As I see,
NAT IPs are not relevant to software backup and it will be better 
to ignore them and not trying to resolve.

There is any option at legato administration program to avoid software 
to try every IP that is configured at machine external interface?

Thank you in advanced.

Best Regards,

--

o o o  Manel Rodero                   | LCFIB - UPC
o o o  Helpdesk Manager               | Campus Nord - Modul B6
o o o  Laboratori de Calcul           | Jordi Girona, 1-3
U P C  Facultat Informatica Barcelona | 08034 Barcelona (Spain)
                                      |
       manel AT fib.upc DOT edu              | Tel: +00 34 93 401 6940
       http://www.fib.upc.edu/~manel  | Fax: +00 34 93 401 7040

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER