Bug #11923
closedInput validation not working for 1:1 NAT entries using an alias as a destination
100%
Description
We have some NAT 1:1 configured with the "Destination" field with alias.
Today we discovered that we could not either add or modify any NAT with a destination alias, the answer will be:
The following input errors were detected:
The destination address is not from the specified address family.
The NAT I'm tryin to edit contain the following parameters:
Interface: LAN
Address Family: IPv4
External subnet IP: Single Host - 10.xx.224.0
Internal IP: Network - 10.xx.0.0/24
Destination: Single host or alias - Our_Object_Alias
The alias "Our_Object_Aliases" contain:
10.xx.128.32/29
10.xx.128.40/29
With pfSense version 2.4.5-p1 work without problem, with pfSense 2.5.0 and 2.5.1 we receive the error.
Files
Updated by Viktor Gurov over 3 years ago
- Category changed from NAT Reflection to Rules / NAT
- Status changed from New to Duplicate
Duplicate of #11751
Updated by Viktor Gurov over 3 years ago
- Status changed from Duplicate to New
I can reproduce it on 2.5.1 and 2.6.0.a.20210514.0100
Updated by Viktor Gurov over 3 years ago
Updated by Jim Pingle over 3 years ago
- Status changed from New to Pull Request Review
- Target version set to 2.6.0
- Plus Target Version set to 21.09
Updated by Viktor Gurov about 3 years ago
- Status changed from Pull Request Review to Feedback
- % Done changed from 0 to 100
Applied in changeset 04857433ff068382f75340e140a60c5acbd1e69c.
Updated by Alhusein Zawi about 3 years ago
- Status changed from Feedback to Resolved
I was able to add and modify 1:1 NAT with a destination alias without errors.
Fixed
2.6.0.a.20210522.0100
Updated by Jim Pingle about 3 years ago
- Target version changed from 2.6.0 to 2.5.2
Updated by Jim Pingle almost 3 years ago
- Subject changed from NAT 1:1 fail to validate aliases to Input validation not working for 1:1 NAT entries using an alias as a destination
Updating subject for release notes.
Updated by Evan Hellman almost 3 years ago
- File Capture1.PNG Capture1.PNG added
- File Capture2.PNG Capture2.PNG added
Confirmed that bug is still present in 2.5.2. Running most recent version and I cannot create 1:1 NAT mappings with aliases. This appears to still affect only 1:1 NAT configurations but now affects the internal and external IP fields.
Updated by Jim Pingle almost 3 years ago
- Plus Target Version changed from 21.09 to 22.01