Project

General

Profile

Actions
Copy link

Bug #277

closed

Auto-generated NAT rules for AON use wrong interface name in descriptions

Added by Fred Taylor-Young almost 15 years ago. Updated almost 15 years ago.

Status:
Resolved
Priority:
Low
Assignee:
-
Category:
Rules / NAT
Target version:
-
Start date:
01/04/2010
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

When switching from "Automatic outbound NAT rule generation (IPsec passthrough)" to "Manual Outbound NAT rule generation (Advanced Outbound NAT (AON))", a set of rules are generated, presumably to keep things working until you create your own...

From the rules my installation* generated for me, I can see that it generated four rules for each active non-WAN interface.
The description for all eight rules is similar to this: "Auto NAT-T created rule for WAN". I have also attached a screenshot of all the auto-generated rules.

However, one would expect the first four rules to be named something like this: "Auto NAT-T created rule for LAN" and "Auto NAT-T created rule for LAN2"

* 2.0-BETA1 built on Mon Jan 4 02:55:57 EST 2010

PS. Why is more than one nonat TFTP proxy rule created? Another bug?

Files

Han.fr3d.org_-_Firewall_NAT_Outbound_-_Mozilla_Firefox_3.6_Beta_5_41274.png (84.5 KB) Han.fr3d.org_-_Firewall_NAT_Outbound_-_Mozilla_Firefox_3.6_Beta_5_41274.png Screenshot of auto-generated advanced outbound NAT rules Fred Taylor-Young, 01/04/2010 08:02 PM
Actions
Copy link
 #1

Updated by Chris Buechler almost 15 years ago

  • Status changed from New to Resolved

It is the correct interface description, as they're all for WAN, just didn't mention previously which internal interface it was for. The TFTP entry shouldn't have been there at all.

I just fixed all this and some other outbound NAT issues I noted while working on that.

Actions
Copy link

Also available in: Atom PDF