Messages

I think the settings entered in the CLI should be copied forward into the Wizard.  Only questions not asked in CLI should be new and started with Wizard defaults.

On Backup, I deleted the NAT rules, and Virtual IPs.  The High Availability > pfsync Synchronize States is already unchecked.  Manually recreating Virtual IPs on Backup does allow vhid # to match the Primary's.

Deleted the manual Virtual IP on Backup again, set sync again, and resynced Primary to Backup worked this time.  Perhaps I did something wrong the first few times.

Thanks.

Primary opnsense with Virtual IP: CARP, 192.168.2.1, VHID Group 1.
Backup opnsense with Virtual IP: CARP, 192.168.2.1, VHID Group 1 not allowed.

I thought the VHID must be the same on both the Primary and Secondary?
The Backup opnsense returns:

"The following input errors were detected:
  * This IP address is being used by another interface or VIP."

The XMLRPC made every Virtual IP on the Backup have a unique VHID.  That seems to go against the examples in https://www.freebsd.org/doc/en/books/handbook/carp.html.  It is not the way I have my existing pfsense 2.2 set up.

At what version of pfsense was opnsense forked?

From CLI console:
4) Reset to factory defaults
3) Set interface IP address
LAN
192.168.1.50/24
Enable DHCP server:
Start: 192.168.1.100
End: 192.168.1.245
Keep https.

Go to client, get IP address (note it will be the correct .100 that you will get), login, finish guided setup, reload.
Log back in.
Go to DHCP Server > LAN tab
The Start address is 192.168.1.10 instead of the .100 set in CLI.

web GUI >
Configure WAN Interface >
Static IP Configuration >
Upstream Gateway is empty instead of what I filled out in CLI console.

I typed in the starting DHCP address pool as *.*.*.100
and ending with *.*.*.245
It all looks fine, but the web GUI shows the staring address pool as *.*.*.10 instead of .100.
Updating the web GUI does correctly change the starting address to *.100.

This issue exists in pfSense 2.2 and 2.2.2 as well.