vyatta wan load balance project (mirror of https://github.com/vyos/vyatta-wanloadbalance.git) https://git.amelek.net/vyos/vyatta-wanloadbalance.git/atom?h=napa 2011-03-30T19:09:58+00:00 2011-03-30T19:09:58+00:00 Michael Larson mike@vyatta.com 2011-03-30T19:09:58+00:00 urn:sha1:25eef8bfb91c2c57907ab79f4ba6bcd9fe0064cb Add the ability to run a user defined script to determine wan load-balancing interface health includes sample http test (scripts/http_test.pl). Configuration will look as follows: wan { interface-health eth0 { nexthop 10.3.0.1 test 1 { test-script /tmp/http_test.pl type user-defined } } interface-health eth1 { nexthop 10.3.0.1 test 1 { test-script /tmp/http_test.pl type user-defined } } With corresponding output: vyatta@vyatta# run show wan-load-balance Interface: eth0 Status: active Last Status Change: Wed Mar 30 19:03:59 2011 +Test: user Script: /tmp/http_test.pl Last Interface Success: 0s Last Interface Failure: n/a # Interface Failure(s): 0 Interface: eth1 Status: failed Last Status Change: Wed Mar 30 19:03:59 2011 -Test: user Script: /tmp/http_test.pl Last Interface Success: n/a Last Interface Failure: 0s # Interface Failure(s): 52 Scripts returns 0 for success, non-zero for failure. 2011-02-12T18:26:09+00:00 Michael Larson mike@vyatta.com 2011-02-12T18:26:09+00:00 urn:sha1:f26ace5c9f88cbf842e8566dbc2656e61e55ff08 2011-02-12T01:38:23+00:00 Michael Larson mike@vyatta.com 2011-02-12T01:38:23+00:00 urn:sha1:1c97581618cab567c9bc3ce230f1ee6fe63eaadb 2011-02-12T01:00:21+00:00 Michael Larson mike@vyatta.com 2011-02-12T01:00:21+00:00 urn:sha1:6d7a9af931280ea0e796b2736b56260becfb3a43 2011-02-01T19:20:34+00:00 Michael Larson mike@vyatta.com 2011-02-01T19:18:38+00:00 urn:sha1:bef6e6090e0d6f11205942c78af313b554dddda5 2011-01-05T19:50:53+00:00 Michael Larson mike@vyatta.com 2011-01-04T18:39:49+00:00 urn:sha1:5932b3640418ef157ef443a1cb62a1c8e666215e (cherry picked from commit cf1754c28af9dc17f5dea4995049823dc7687a63) 2011-01-05T19:50:44+00:00 Michael mike@vyatta.com 2010-12-30T11:51:46+00:00 urn:sha1:7f19756f2dc78d183cdff49ddcab5817625115e0 default to no dns resolution with option for dns resolution on op mode command. (cherry picked from commit 9e9c03edd4d4b2c87f0da68c8b40c216a324495b) 2010-08-26T19:04:19+00:00 Michael Larson slioch@slioch.vyatta.com 2010-08-26T19:04:19+00:00 urn:sha1:ec93cf04b77bb8da5c731e34843694a61fa0edf6 remove policy route on shutdown. 2010-08-26T17:38:18+00:00 Michael Larson slioch@slioch.vyatta.com 2010-08-26T17:38:18+00:00 urn:sha1:55a1515e13b1eb22725ec619421aa193e7b662ce new warnings are generated for the following conditions exclude rule that has an outbound interface defined rule with no outbound interfaces defined (and is not an exclude rule) 2010-08-06T16:34:40+00:00 Michael Larson slioch@slioch.vyatta.com 2010-08-06T16:29:50+00:00 urn:sha1:7e5fba4962deeef9d5c783063ea4f9d9ea0e75da The problem was introduced when the start order for WLB and pppoe interfaces changed (must have been sometime pre-kenwood). The pppoe hook script was checking for the existence of WLB prior to updating the nexthop information for WLB. The fix is to perform the update without this check and WLB will pick up the changes when it is eventually started.