vyatta-nat.git/scripts, branch current Vyatta configuration/operational commands for NAT (mirror of https://github.com/vyos/vyatta-nat.git) https://git.amelek.net/vyos/vyatta-nat.git/atom?h=current 2019-01-29T13:45:34+00:00 T166: Changed NPTv6 to use NETMAP 2019-01-29T13:45:34+00:00 Merijn Evertse merijn@trans-ix.nl 2019-01-29T13:45:34+00:00 urn:sha1:6f79779ecf9ada95a13c15997810ca5c21ce7db3 vyatta-nat: only create nat object for testing changed or added rules 2015-11-28T19:53:49+00:00 Alex Harpin development@landsofshadow.co.uk 2015-11-28T19:53:49+00:00 urn:sha1:983f6e24e0cacee1fbb490a8003814a026a3cc8d Only create a new source or destination NAT object when testing changed or added NAT rules to reduce testing overhead. Bug #493 http://bugzilla.vyos.net/show_bug.cgi?id=493 vyatta-nat: formatting changes for style consistency 2015-11-28T19:45:19+00:00 Alex Harpin development@landsofshadow.co.uk 2015-11-28T19:45:19+00:00 urn:sha1:a5c142516d6ce7f3a46b9d35d17dfe076a711ce2 Update scripts/vyatta-update-dst-nat.pl and scripts/vyatta-update-src-nat.pl to maintain style and consistency. vyatta-nat: check nat rules for errors before processing them for real 2015-07-19T09:27:34+00:00 Alex Harpin development@landsofshadow.co.uk 2015-07-19T09:18:30+00:00 urn:sha1:84b4345897825efd8f2ac6144f16a501f1b157e5 Errors in both source and destination NAT rules can cause either rules to be overwritten (completely or partially), dropped entirely, or just ending up with an inconsistent state in comparison to the current configuration. This can lead to unpredictable NAT results, which can't even be corrected by deleting all the nat rules, only a reboot will correct the issue. Checking these rules for consistency in a separate loop before they are applied allows the errors to flagged up and the commit failed before the nat table is touched. Bug #493 http://bugzilla.vyos.net/show_bug.cgi?id=493 Revert "vyatta-nat: check nat rules for errors before processing them for real" 2015-07-19T09:14:44+00:00 Alex Harpin development@landsofshadow.co.uk 2015-07-19T09:14:44+00:00 urn:sha1:5d5445e1b1851e7e0a150ad53e7286f98b20b039 This reverts commit 5f05bdd480f0de2be2d87934b9b53dab09ead9ea. vyatta-nat: check nat rules for errors before processing them for real 2015-07-12T16:17:58+00:00 Alex Harpin development@landsofshadow.co.uk 2015-07-12T16:17:58+00:00 urn:sha1:5f05bdd480f0de2be2d87934b9b53dab09ead9ea Errors in both source and destination NAT rules can cause either rules being overwritten or partially, dropped entirely or just end up with an inconsistent state in comparison to the current configuration. This can lead to unpredictable NAT results, which can't even be corrected by deleting all the nat rules, only a reboot will solve them. Checking these rules for consistency in a separate loop before they are applied allows the errors to flagged up and the commit failed before the nat table is touched. Bug #493 http://bugzilla.vyos.net/show_bug.cgi?id=493 Add initial support for NPTv6 (#387) 2015-02-15T21:37:14+00:00 kouak kouak@kouak.org 2015-02-15T21:37:14+00:00 urn:sha1:9571f0e592088c49c6c16724c5124631326066fd Fix condition of all_deleted 2014-03-19T08:52:08+00:00 Yuya Kusakabe yuya.kusakabe@gmail.com 2014-03-19T08:52:08+00:00 urn:sha1:5e481bb09c538fcf69eb9669beef2448a6cef9e5 Bug #8331: provide rule number in commit error message. 2013-11-10T14:46:27+00:00 Daniil Baturin daniil.baturin@vyatta.com 2013-05-29T14:09:17+00:00 urn:sha1:14bf61dea0966201caf34c8e7cdf9e23fbcb85bf Don't display masquerade rule code help for destination rules. 2012-01-03T18:10:18+00:00 Daniil Baturin daniil.baturin@vyatta.com 2012-01-03T18:10:18+00:00 urn:sha1:424188ecefb15b13614b5e74ccf25c5652de5d75