Bug #4251


NAT Reflection not working if LAN is bridged

Added by Frederic Steinfels over 7 years ago. Updated about 3 years ago.

NAT Reflection
Target version:
Start date:
Due date:
% Done:


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


I have been trying everything to get NAT reflection working. My last effort was to remove LAN bridge (which I wasn't really using anymore). And voila, NAT Reflection was working after loading the modified XML config without any interaction or changes - just a reboot.

I am 100% sure, that there are no other changes were made besides removing the brdige and moving DHCP Server (and everything else) to the LAN interface.

I am 100% sure that NAT reflection was not working before no matter what combination of settings I have tried.
I am 100% sure that NAT reflection is working now.

Actions #1

Updated by Chris Buechler over 7 years ago

  • Status changed from New to Feedback
  • Target version deleted (2.2)

what was LAN bridged to? Was there an IP on the bridge itself or was it on the LAN interface?

Actions #2

Updated by Frederic Steinfels over 7 years ago

It was bridged with an OpenVPN PSK TAP Client. That connection has been down for about a month but was not disabled. I have just disabled it :-)

Actions #3

Updated by Frederic Steinfels over 7 years ago

The only other explanation that came to my mind is that nat reflection might need a reboot to activate under some circumstances. This might be really hard to figure out. Furthermore I have made various reboots due to version upgrades. However only recently I tried a minimal setup with reflection disabled globally but only pure nat added to a few essential rules.

Actions #4

Updated by Jim Pingle about 3 years ago

  • Status changed from Feedback to Closed

This is almost certainly solved via pure NAT reflection. Open a new issue with current info if it is not.


Also available in: Atom PDF