Joshua Baker-LePain wrote:
On Thu, 10 Jun 2004 at 1:40pm, Paul Bijnens wrote
I have been thinking about this problem, and, without any real testing to backup my hypothesis, I believe the problem lies in the default timeout in iptables for UDP traffic, as you decided too.
For TCP traffic, once a packet is replied, the timeout becomes very large (5 days or so I believe). But for UDP, which is a conectionless protocol the timeout is 180 seconds (I believe). After this timeout the connection tracking drops the rule.
Is this true even with ip_conntrack_amanda loaded?
I should have a look at the source code, or find a detailed doc that explains it, to find out.
Anyway that module should somehow know the etimeout parameter of amanda.conf, which of course it does not know, or otherwise allow a really really large timeout, like a few hours. Or should be tuneable somehow (in the amanda-tradition that could be hardcoded at compile time).
-- Paul Bijnens, Xplanation Tel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *********************************************************************** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***********************************************************************
