Feature #7705

Support dynamic interface address for 1:1 NAT

Added by Riccardo Paolo Bestetti over 3 years ago. Updated 6 months ago.

Rules / NAT
Target version:
Start date:
Due date:
% Done:


Estimated time:
Release Notes:


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).

Associated revisions

Revision e5e7d84c (diff)
Added by Viktor Gurov 10 months ago

Support dynamic interface address for 1:1 NAT. Implements #7705


#1 Updated by Jim Pingle over 1 year ago

  • Category set to Rules / NAT

#3 Updated by Jim Pingle 10 months ago

  • Status changed from New to Pull Request Review
  • Target version set to 2.5.0

#4 Updated by Renato Botelho 10 months 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!

#5 Updated by Steve Beaver 6 months ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF