Project

General

Profile

Bug #402

External address "any" doesn't set "any" in rdr

Added by Chris Buechler over 9 years ago. Updated over 9 years ago.

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

0%

Estimated time:
Affected Version:
2.0
Affected Architecture:

Description

For instance, this config:

                <rule>
                        <external-address>any</external-address>
                        <protocol>tcp</protocol>
                        <external-port>80</external-port>
                        <target>1.2.3.1</target>
                        <local-port>3128</local-port>
                        <interface>lan</interface>
                        <descr/>
                        <associated-rule-id>nat_4b906a03f35e42.23599161</associated-rule-id>
                </rule>

results in:

rdr  on em1 proto tcp from any to 192.168.1.1 port 80 -> 1.2.3.1 port 3128

when it should be s/192.168.1.1/any/ as external address is set to any. Resulting rule should be:

rdr  on em1 proto tcp from any to any port 80 -> 1.2.3.1 port 3128

Associated revisions

Revision 2993dcc2 (diff)
Added by Erik Fonnesbeck over 9 years ago

Ticket #402. Check for external address of "any" on port forwards, since alias_expand only returns null in that case, and the port forward code would then use the IP address as the fallback.

History

#1 Updated by Erik Fonnesbeck over 9 years ago

Committed a fix.

#2 Updated by Chris Buechler over 9 years ago

  • Status changed from New to Resolved

fixed

Also available in: Atom PDF