vyatta-cfg.git, branch jenner Vyatta configuration system (mirror of https://github.com/vyos/vyatta-cfg.git) https://git.amelek.net/vyos/vyatta-cfg.git/atom?h=jenner 2009-12-16T20:18:16+00:00 0.14.91+jenner53 2009-12-16T20:18:16+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2009-12-16T20:18:16+00:00 urn:sha1:2b43ed37a5f0d154cdbc7ca8832218c11914a0d8 Check proper state on DHCP renew/release 2009-12-16T20:16:30+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2009-12-16T20:16:30+00:00 urn:sha1:becbaf92760f1f5a9c586acd66ae901fbcf1c855 Bug 3917 Need to check current state when in operational mode (not config state). 0.14.91+jenner52 2009-12-15T00:50:57+00:00 Michael Larson slioch@slioch.vyatta.com 2009-12-15T00:50:57+00:00 urn:sha1:945fb88d7ad13e467b9109bdc3919f105595ee74 fix for bug 4999 2009-12-15T00:49:32+00:00 Michael Larson slioch@slioch.vyatta.com 2009-12-02T01:05:30+00:00 urn:sha1:0bf36f892de68c91f62da36cc0e20473f338f860 0.14.91+jenner51 2009-12-14T23:40:25+00:00 Mohit Mehta mohit.mehta@vyatta.com 2009-12-14T23:40:25+00:00 urn:sha1:a47a1fd6552bb413789d44efef96b699d110f458 Jenner Fix for Bug 5026 - NAT rule not taking effect on specific value 2009-12-14T23:33:41+00:00 Mohit Mehta mohit.mehta@vyatta.com 2009-12-14T23:33:41+00:00 urn:sha1:829762ea92584e005d6c505180aaccfff08bb58d Moving NAT to a higher priority to be right after firewall and before interfaces and routing configuration to prevent connections from getting tracked before firewall and NAT have been setup need to clean up /tmp/.changes file after work is done during commit 2009-12-02T00:48:36+00:00 Michael Larson slioch@slioch.vyatta.com 2009-12-02T00:48:36+00:00 urn:sha1:8a659f0623895905f5c2c5f2ec535e9a0770478e 0.14.91+jenner50 2009-11-20T01:22:57+00:00 Bob Gilligan gilligan@vyatta.com 2009-11-20T01:22:57+00:00 urn:sha1:8f053013ab474ad34b05ad518cbc94f4b4530af8 Remove default value for "smp_affinity". 2009-11-20T01:20:19+00:00 Bob Gilligan gilligan@vyatta.com 2009-11-20T01:20:19+00:00 urn:sha1:5687f402dea85d1bcb2450ee7a4c0ac695112909 Out of an abundance of caution, we don't want to introduce a default value for a parameter that previously had none without more extensive testing, as it would affect all systems. We will introduce the default value in the next release. 0.14.91+jenner49 2009-11-18T01:07:13+00:00 Bob Gilligan gilligan@vyatta.com 2009-11-18T01:07:13+00:00 urn:sha1:3c2806b074713575e820db16d68b9c25c80b3729