vyatta-wanloadbalance.git/src, branch larkspur vyatta wan load balance project (mirror of https://github.com/vyos/vyatta-wanloadbalance.git) https://git.amelek.net/vyos/vyatta-wanloadbalance.git/atom?h=larkspur 2010-09-10T17:48:51+00:00 fix one more case 2010-09-10T17:48:51+00:00 An-Cheng Huang ancheng@vyatta.com 2010-09-10T17:48:51+00:00 urn:sha1:31683647e88573d389e7cec895757b72e2b25828 (cherry picked from commit 4bea392ff2eb1f232f8c76d84aa24d6ba7201670) Conflicts: src/rl_str_proc.cc fix for bug 6029 2010-09-10T17:47:00+00:00 An-Cheng Huang ancheng@vyatta.com 2010-08-11T17:06:17+00:00 urn:sha1:4e81761f837baab857defe3e4c7c9663f3c2a4e0 * fix 64-bit problem: string::*find*() functions have return type of "size_t", not "unsigned int". (cherry picked from commit 01cabdb0c9003a37e5801667bd408d6c2c7126b6) fix for bug 6019 2010-08-10T20:03:03+00:00 An-Cheng Huang ancheng@vyatta.com 2010-08-10T17:21:53+00:00 urn:sha1:4ef8d4b4d965c51359aad13957e4b26b8b58a990 * fix 64-bit problem: string::find*() functions have return type of "size_t", not "uint32_t". (cherry picked from commit f5e3af905e1c37d53d1a0d7de1c3d457dd4cb632) fix for bug 5583. 2010-07-16T22:19:13+00:00 Michael Larson slioch@slioch.vyatta.com 2010-07-16T22:19:13+00:00 urn:sha1:063be62a70d2b15b19cb92a353129652e1682283 added syslog messages on failure to insert default route into policy 2010-06-21T16:31:48+00:00 Michael Larson slioch@slioch.vyatta.com 2010-06-21T16:31:48+00:00 urn:sha1:b964b6084486e8c900958fd3cbec252b7936a16d table. submission in reponse to forum posting on multiple entries found in snat table with adsl dhcp configuration: 2010-06-20T01:51:16+00:00 Michael Larson slioch@slioch.vyatta.com 2010-06-20T01:51:16+00:00 urn:sha1:ef4a85e5b5fe554137f923a156b5537ff5d54216 http://www.vyatta.org/forum/viewtopic.php?t=4254 fix for bug 5520. 2010-04-06T18:40:25+00:00 Michael Larson slioch@slioch.vyatta.com 2010-04-06T18:40:25+00:00 urn:sha1:c61afbea231483f7c33e37bfc1aa258fca0c6c3f When checking policy route compare nexthop and interface rather then just checking for an entry. This allows for incorrect entries to be replaced. This would be a problem if different nexthop is readvertised via dhcp to the interface. when a test is not configured the response time window is incorrectly scaled into milliseconds, therefore without a configured test it is much more likely that a ping test 2010-03-23T22:22:01+00:00 Michael Larson slioch@slioch.vyatta.com 2010-03-23T22:22:01+00:00 urn:sha1:2e5982e8d48b6893cdbd785be21da54515ea78d7 will fail. the work-around is to configure a test (response time is not required as the default value of 5 seconds will be used at this point). fix debug state for test modules. debug flag was not being initialized correctly when configured. 2010-03-23T21:22:53+00:00 Michael Larson slioch@slioch.vyatta.com 2010-03-23T21:22:53+00:00 urn:sha1:62cf04bb7b19058fe2490ca6cd821273da56b67d need to close file when configured for dhcp on ppp interface--file handle leak otherwise. 2010-03-19T22:58:02+00:00 Michael Larson slioch@slioch.vyatta.com 2010-03-19T22:58:02+00:00 urn:sha1:570ae4072bf30c5570cf51b555ff7d6354debb4f