Messages

Version 20.7.3

Seems to have been broken since 20.7, any ideas? Running Unbound DNS with "register DHCP hostnames" checked. Makes no diff.

I had the same problem until I installed 20.7.3, and now it reboots in less than 2 minutes. Have you tried rebooting since upgrading? Seems to have fixed it for me.

Still happening with me, at ~24 days uptime. This time I can't even read any of the logs or my SSH session freezes up. @dedi did you find a solution?

Same problem but it worked from another computer... and started working again on same computer for no apparent reason. No reboot, no configuration changes.

Its just kind of confusing since there's an option for it (NAT Reflection_ --that doesn't work, when you set up a port forward.

[Firewall -> Settings -> Advanced]

Why? This is the same exact issue as @BeanAnimal and others, it's usually good forum etiquette to search for related topics instead of everyone creating a separate thread for the same problem...?

I just resolved it though, I don't know if this is the "proper" way, but go to Firewall -> Settings -> Advanced
and check "Reflection for port forwards", and for good measure "Reflection for 1:1", and "Automatic outbound NAT for Reflection".

Hopefully this helps someone else, and I hope I haven't just created some nasty loops but so far so good.

I tried it the "oldschool" way like BeanAnimal suggested, and it's still broken, and seems to have broken unbound DNS as well, no idea why.

Same problem, very frustrating. Might switch to PFsense or EdgeRouter because of this.

A workaround might be to use Unbound DNS and create an override entry for your web server's internal IP.

I am having the same issue, NAT reflection not working. I ended up making an override entry in Unbound for my internal webserver, but it only works if the client machine uses my internal dns server, which is handed out via DHCP, but anyone who sets it manually, the website resolves as my external IP, and doesn't NAT to the internal IP of the webserver.

Seems to me this should be as simple as enabling "NAT reflection" in the port forward rule. Is this a bug or are we missing something? Using version 20.7.