[Per Yngve Berg]

Use the default ports and assign an IP Address to each Docker Container.

[l_a_n_f_e_a_r]

Thank you for this post! I was having this specific issue after doing some updates and trying to enable this feature and it was causing me grief since everything else seemed to be working cleanly with this config change.

So, as of build DD-WRT v3.0-r58531, turning on `Shortcut Forwarding Engine` does indeed still seem to break NAT loopback as described in the original message.

Some points of emphasis here:

- I am simply trying to push forward info to continued users of the firmware
- I do not expect a fix for this because (as mentioned earlier in thread) CTF is a BroadCom black-box binary that I appreciate was brought in with any level of support, even with conditions like this
- It makes sense to me that a feature dealing with 'hardware accelerated NAT translation' (apologies if some technical detail with that statement is inaccurate) would interfere with NAT routing behavior
- And when it's passed off to a black-box binary interfacing directly with hardware that there would be limited control over options deal with bugs or routing
- FWIW, i was able to use configuration 'Shortcut Forwarding Engine: SFE' and 'Flow Acceleration: CTF & FA' and NAT loopback does work
- I do not know for sure if any of the advice in previous posts are valid work-arounds, I was not excited about reconfiguring DNSMasq and other features that otherwise work as of now, and I host multiple domains so trying to redirect several DNS entries + ports to target services wasn't something I tried fighting very hard. I simply was dealing with toggling the CTF, SFE and FA options.

So, thanks for all the hard work on this project. If there is ever an update to this, bonus. In the meantime, just trying to pass along information.[/b]

[jwh7]