As someone suggested, you might try using different firmware. There are
a lot of options for these linksyses. DD-WRT is definitely one of them
but I personally prefer tomato.
James Harper wrote:
I think that makes any Bacula job longer than 10 minutes impossible
using
this
On Thursday 01 February 2007 01:48, James Harper wrote:
I think that makes any Bacula job longer than 10 minutes impossible
using
this Linksys router. Looks like I'm out of luck. I have updated to
the
newest firmware, and the Linksys config doesn't have any ability to
modify
the
Try:
echo 300 /proc/sys/net/ipv4/tcp_keepalive_time
echo 60 /proc/sys/net/ipv4/tcp_keepalive_intvl
echo 10 /proc/sys/net/ipv4/tcp_keepalive_probes
This will send the first keepalive after 5 minutes, and then every
60
seconds after that, and will drop the connection if no
Yes, providing you don't mind prematurely killing off non-keepalive
programs
that are inactive during the reduced keepalive period you have set.
This should be relatively easy to test... assuming we can't find a
document somewhere that clarifies it one way or another.
Okay... if you
Yes, providing you don't mind prematurely killing off non-keepalive
programs
that are inactive during the reduced keepalive period you have set.
I couldn't find anything definitive in the kernel source, but looking
through it did remind me of the TCP_KEEPIDLE, TCP_KEEPINTVL, and
TCP_KEEPCNT
On Thursday 01 February 2007 12:19, James Harper wrote:
Try:
echo 300 /proc/sys/net/ipv4/tcp_keepalive_time
echo 60 /proc/sys/net/ipv4/tcp_keepalive_intvl
echo 10 /proc/sys/net/ipv4/tcp_keepalive_probes
This will send the first keepalive after 5 minutes, and then every
60
On Thursday 01 February 2007 13:10, James Harper wrote:
Yes, providing you don't mind prematurely killing off non-keepalive
programs
that are inactive during the reduced keepalive period you have set.
I couldn't find anything definitive in the kernel source, but looking
through it did
On Thursday 01 February 2007 12:34, James Harper wrote:
Yes, providing you don't mind prematurely killing off non-keepalive
programs
that are inactive during the reduced keepalive period you have set.
This should be relatively easy to test... assuming we can't find a
document
Aaah, I've finally figured it out. The very common Linksys WRT54G v5 router IS
dropping inactive sockets after exactly 10 minutes.
I verified this through a process of elimination. Any time the Linksys router
was used, I'd get a socket drop at 10 minutes (wireless or ethernet cable
On Wed, 2007-01-31 at 11:05 -0800, Brad Peterson wrote:
Aaah, I've finally figured it out. The very common Linksys WRT54G v5
router IS dropping inactive sockets after exactly 10 minutes.
I verified this through a process of elimination. Any time the
Linksys router was used, I'd get a
Kern, if you are reading this, what are the chances that a
heartbeat could be implemented between the director and the storage
daemon?
Would there be any significant downsides to a global heartbeat
directive in the director? When the director initially connects to an
FD/SD it could
Kern, if you are reading this, what are the chances that a heartbeat could
be implemented between the director and the storage daemon?
Yes, that is possible, but you will need to find someone to program it.
If I knew my C++ well enough, I'd dive into it. :) Darn my lack of C++
knowledge.
On Wed, 31 Jan 2007, Brad Peterson wrote:
Aaah, I've finally figured it out. The very common Linksys WRT54G v5
router IS dropping inactive sockets after exactly 10 minutes.
Set heartbeat intervals to 1 minute.
Problem solved (and is why this directive is there)
On Wed, 31 Jan 2007, Kern Sibbald wrote:
I personally I would ask for a refund on the router since it apparently
doesn't understand keepalive and doesn't follow standard TCP/IP standards so
does not function properly.
Fat chance of that. Linksys are notorious for lack of response to consumer
Aaah, I've finally figured it out. The very common Linksys WRT54G v5
router IS dropping inactive sockets after exactly 10 minutes.
Set heartbeat intervals to 1 minute.
Problem solved (and is why this directive is there)
I already have the heartbeats in at 30 seconds each. Unfortunately,
On Wed, 2007-01-31 at 13:40 -0800, Brad Peterson wrote:
Aaah, I've finally figured it out. The very common Linksys WRT54G
v5
router IS dropping inactive sockets after exactly 10 minutes.
Set heartbeat intervals to 1 minute.
Problem solved (and is why this directive is there)
I
I think that makes any Bacula job longer than 10 minutes impossible
using
this Linksys router. Looks like I'm out of luck. I have updated to
the
newest firmware, and the Linksys config doesn't have any ability to
modify
the timeout value. I suppose I could buy a new router, or set up a
new
For now, I'm giving up on having an offsite storage daemon. I don't
have the money to spend on a fully working router. So I'm going to
just keep the storage daemon on the same machine as the director,
and
then rsync the physical volumes afterwards offsite.
Though this is better
18 matches
Mail list logo
