Differences between version 6 and revision by previous author of FailoverInternetConnection.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 6 | Last edited on Wednesday, January 12, 2005 12:18:47 am | by EeroVolotinen | Revert |
| Older page: | version 3 | Last edited on Friday, July 4, 2003 2:45:42 pm | by CraigBox | Revert |
@@ -89,7 +89,30 @@
Another method is to use [Nagios]. I have a eventhandler that I wrote for nagios, but I never got it working nicely, hence writing my own above. I can provide it as a sample, however I think the issues were due to the link going to a hard critical state straight away, and not being in a warning state for any length of time.
-- DanielLawson
+
+
+-
+
+Just little notice from Eero, I don't even know if this is correct, but:
+
+http://www.pcquest.com/content/linux/103091901.asp says something about gc_timeout?
+
+If this is correct I only need to set 2 gateway cards and enter something like that:
+
+# route add default gw 192.168.1.2 dev eth0 metric 0
+# route add default gw 192.168.2.2 dev eth1 metric 10
+# echo 300 > /proc/sys/net/ipv4/route/gc_timeout or sysctl net.ipv4.route.gc_timeout = 300
+
+Usually best way is to put sysctl settings to /etc/sysctl.conf
+
+and kernel automagically monitors lines and uses better? I haven't tested this not yet, but
+I will soon.
+
+
+
+
+-- Eero Volotinen (eero@jlug.fi)
-----
CategoryNetworking
