1
20.1 Legacy Series / Outbound NAT not working after reboot
« on: November 17, 2020, 10:25:45 am »
Hi,
we are experiencing a strange problem on our opnsense box. Our outbound nat is set to manual mode and we have defined quite a lot outbount nat rules. While running everything is working fine. As soon as I reboot the opnsense box the outbound nat rules stop working.
After the reboot I see unnated traffic on the wan interface as allowed by the firewall rules.
As soon as I change any outbound nat rule the rest of the bunch starts working and traffic start to flow.
The one thing special in this case is that we are running a single node cluster (the other cluster member died and is still offline) with several carp virtual ip adresses.
I suspect that shortly after the reboot the virtual ip is not available and the nat rules cannot be applied. Is this a reasonable theory?
Cheers
we are experiencing a strange problem on our opnsense box. Our outbound nat is set to manual mode and we have defined quite a lot outbount nat rules. While running everything is working fine. As soon as I reboot the opnsense box the outbound nat rules stop working.
After the reboot I see unnated traffic on the wan interface as allowed by the firewall rules.
As soon as I change any outbound nat rule the rest of the bunch starts working and traffic start to flow.
The one thing special in this case is that we are running a single node cluster (the other cluster member died and is still offline) with several carp virtual ip adresses.
I suspect that shortly after the reboot the virtual ip is not available and the nat rules cannot be applied. Is this a reasonable theory?
Cheers