We are getting this warning message continually. See attached screenshot.
Can anyone decode this message so we can get rid of it.
Cheers
Spart
So.. This looks to be a fairly similar issue to this one https://github.com/opnsense/core/issues/2841.
Could you try this as mentioned by AdShellevis:
"Can anyone with the issue try to disable "Automatic outbound NAT for Reflection" in Firewall->Advanced and test again? As far as I can see that's these are the only areas in the code generating a rule with as target an interface."
Quote from: cmdr.adama on June 15, 2020, 01:18:39 PM
So.. This looks to be a fairly similar issue to this one https://github.com/opnsense/core/issues/2841.
Could you try this as mentioned by AdShellevis:
"Can anyone with the issue try to disable "Automatic outbound NAT for Reflection" in Firewall->Advanced and test again? As far as I can see that's these are the only areas in the code generating a rule with as target an interface."
That tracks with what we did to try and get reflection working. We set Automatic outbound NAT for Reflection on and reflection is now working for the lan.
If we disable it Nat reflection does not work.
Cheers
Spart
In that case, it might be worth applying the fix also mentioned in that thread.
Down the bottom there's a fix that should apply for 20.1.7
Quote from: cmdr.adama on June 16, 2020, 01:01:33 AM
In that case, it might be worth applying the fix also mentioned in that thread.
Down the bottom there's a fix that should apply for 20.1.7
As this is a production router I will wait for the formally tested fix to work through the testing and release cycle.
Cheers
Spart