Yann PURSON wrote:
>
> Ok...Now that's rigth I'm passing thru a Firewall with IP masquarading,
> but I'm not sure that it's the pb, because when I try to backup only
> argon it works fine...
>
Firewalls with masquerading bring an extra level of complication. I am
quite sure it has to do with this. As a first measure, check the list
archives using the keywords "NAT", "masquerading", "firewall",
"timeout", separately or in combinations. You will then see what I mean.
As a second measure, investigate the following:
check with ipchains on
your firewall and examine the masquerading timeouts:
ipchains -L -M
should list the timeouts used (among other things)
ipchains -M -S timeout1 timeout2 timeout3
with aproppriate values for timeoutx, x=1,..3 should set new timeouts
(in seconds) for masquerading regarding TCP sessions, TCP sessions after
receiving a FIN packet, and UDP packets, respectively.
Since the defaults as listed in
`/usr/src/linux/include/net/ip_masq.h', are currently 15 minutes, 2
minutes and 5 minutes respectively, you might want to increase them with
the above command and see what happens.
I see a difference of quite exactly 2 minutes between trying and giving
up in your log, so could this be the 2 minutes for "TCP sessions after
receiving a FIN packet", as above?
A third measure could be to investigate where *exactly* the client's
ports are mapped to by your firewall. It might even be that they are
blocked there by a packet filter, by some security software etc. Ask the
firewall's administrator and ... good luck :-)
--
Regards
Chris Karakas
Don´t waste your cpu time - crack rc5: http://www.distributed.net
