Cluster upgrade from 2.1.5 to 2.2.2 Outbound NAT problems

jsnicaise

Hello,

I have a cluster of pfSense nodes. Both were 2.1.5. I've removed the secondary node and rebuilt it from scratch with version 2.2.2.

Everything went fine until it was time to synchronize the configuration. All the configuration seems to synchronize correctly except for the Outbound NAT part. The secondary node (version 2.2.2) stays stuck into Automatic Outbound NAT.

If i change from Automatic Outbound NAT to Manual NAT and push a config sync from the primary node (version 2.1.5), it switches back to Automatic NAT.

The result is the Outbound NAT part does not get synchronized.

Any ideas?

Thanks!

edit: I forgot to mention I also get that error upon synchronization: " pfi_table_update: cannot set 65 new ip addresses into table self: 22 "
edit2: I tried version 2.2 and 2.2.2

jsnicaise

I just did a compare of both configs and they're almost identical (order is a bit different)… The Outbound NAT is present on the second node, just like in the first node..

Two parts differ: the sysctl part: http://pastie.org/10115575

and these couple of lines, under system: http://pastie.org/10115578

I don't see how these lines could be causing problems...

So I'm left with this error being the most relevant:

This is the error I get when the synchronization happens: pfi_table_update: cannot set 65 new ip addresses into table self: 22
This is the error I get when I reboot: pfi_table_update: cannot set 77 new ip addresses into table self: 22

What does that mean?

Thanks,

jsnicaise

https://forum.pfsense.org/index.php?topic=88031.0

https://forum.pfsense.org/index.php?topic=87813.msg483500#msg483500

This should really be in the upgrade notes…