Age | Commit message (Collapse) | Author |
|
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)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fix condition of all_deleted
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
multiport at the same time.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Conflicts:
lib/Vyatta/DstNatRule.pm
|
|
|
|
|
|
options to ensure nothing gets adhered.
|
|
|
|
|
|
|
|
|
|
for any interface.
|
|
|
|
|
|
|
|
translations".
|
|
vyatta-show-nat-statistics.pl name change.
|
|
rename to make more clear what does it do.
|
|
|
|
|