Feature #7705
closed
Support dynamic interface address for 1:1 NAT
100%
Description
Currently, in the 1:1 NAT UI, the "External subnet IP" field cannot be populated with options such as "WAN address" or "WAN subnet", but only with a fixed IP address.
This works fine for access setups such as RFC 1483 "routed", but doesn't work for more modern setups such as multiple PPPoE tunnels over the same Ethernet layer to get multiple dynamic IP addresses.
Use cases are pretty much anything benefitting from end-to-end communications such as gaming, home-hosted servers, home automation/surveillance systems, etc.
The workaround I'm currently using comprises creating Port Forward, Outbound and Policy Routing rules, which enormously complicates the setup for artificial reasons (i.e. the scripts for these features support interface addresses while 1:1 only supports fixed addresses).
Updated by Viktor Gurov over 4 years ago
Updated by Jim Pingle over 4 years ago
- Status changed from New to Pull Request Review
- Target version set to 2.5.0
Updated by Renato Botelho over 4 years ago
- Status changed from Pull Request Review to Feedback
- Assignee set to Renato Botelho
- % Done changed from 0 to 100
PR has been merged. Thanks!
Updated by Anonymous