Hello,
I have a reverse proxy server running, and I've configured a DNAT rule to forward the WAN IP to the reverse proxy server's internal IP address.
The server is accessible from the internet on version 26.1, but it stopped working after upgrading. After reverting back to 26.1, everything works again.
At first, I thought the issue was related to the DNAT rule, but I discovered that the problem only occurs when "Divert to Intrusion Detection" is enabled. If I disable this option, everything works as expected.
(I have a manual firewall rule on the WAN interface that allows traffic to the reverse proxy server's internal IP address.)
There are no alerts shown in the Intrusion Detection logs. However, in the Live View I can see the traffic being marked as Allowed first, followed immediately by Blocked. Once I disable "Divert to Intrusion Detection", the Blocked entry no longer appears, and the reverse proxy becomes accessible again.
Am I missing something, or could this be a regression in the new version?
Kind regards
I had a similar experience. I also have DNAT for a Host and divert-to. After the update this stopped working.
https://github.com/opnsense/src/issues/303
I was already wondering how a dnat bug hadn't been noticed during testing. But when combined with divert-to, it makes sense. I'm glad the bug has now been found. Thanks