@viragomann
i think it's that
https://forum.netgate.com/topic/150505/xmlrpc-restore_config_section-error

because my rule to NAT with CARP ip make the backup node not able to reach the gateway
so as it explain on that like you sent

Filter reload sees the down gateway and resets states, terminating the connection currently used for XMLRPC.

it make sense
Thanks you very much, i think you resolve my issue :)

@kayavila OK this is great info, thank you! I read your entire write up you linked to as well but I'm still trying to wrap my brain around it. Think I've got it figured out but wanted to pose an example.

This particular one will be between different VLAN/subnets rather than with WAN as I personally don't ever allow those connections via the WAN.

So in theory if you had VLAN1 and VLAN2 setup, and there was an any-any rule below a block "This Firewall" rule on VLAN1, and some device on VLAN1 tried to contact the LAN interface of VLAN2, due to state syncing this would be let through? Since the first node would see the connection to the VLAN2 IP and see that it's not in it's block list but matches the any-any rule, and then the state would sync to the secondary which wouldn't assess it's rules?

If that is the case, I would imagine not having a rule on the primary node that allows access to any would solve the issue, but since some people do use an any rule for internet access it could pose a problem (though best practice is of course to use an alias for RFC1918 and explicitly allow the inverse of that).

@viragomann
Thanks !
Went with the port forward + outbound option, NAT is working finally.

@starsandbars What questions do you have after reading this?

https://docs.netgate.com/pfsense/en/latest/highavailability/index.html

@mrfrenchfry
You can export the interface config from the secondary node:
Diagnostics > Backup & Restore > Backup & Restore
At Backup area select "Interfaces".

Download the file. Then load it into a text editor and order the interfaces accordingly to the primary.

Save the file and re-import it into the secondary.

More photos:

20220201_181442.jpg
20220131_180718.jpg
20220201_181457.jpg
20220119_165632.jpg
20210929_162052.jpg 20201214_141056_HDR.jpg

Sorry, it probably was only a temporary problem while the network reconfigured to the static IP.
It now seems to work properly.

@skorpio The CARP alias skew is set in each alias: https://docs.netgate.com/pfsense/en/latest/recipes/high-availability.html#configuring-the-carp-virtual-ips

"A primary node is typically set to 0 or 1, secondary nodes will be 100 or higher. This adjustment is handled automatically by XML-RPC synchronization."

@crl was this resolved? I'm having some issues myself.

Hoping you found your solution. :)

@viragomann switching to CARP VIP in the OpenVPN config solved the issue, now I'm getting to the LAN. Thank you very much for pointing me on the right direction!

Ok, found out the problem, maybe.

there was a space in the Gateway IP in VAN50 dhcp settings also checked "Time from UTC to Local"

With both changes, now DHCP works flawlessly.

Thank you.

@steveits
Hello,
When I add the rule on the master, it is duplicated on the second pfsense. The master pfsense remains master in "status/CARP".
The second pfsense is in "Backup".
Yes the problem is not temporary, I have a total loss to the internet.
The master's wan interfaces are up and communicating with their gateway. But unable to access the internet.
The interfaces are in green on the dashboard.

Regards.

Is any one knows why the URL is getting changed by adding amp; every time while saving the configuration? this is kind of miss-behavior