Score:0

PFsense High-Availability - issues with sync of VLAN interface

cn flag

So I am trying to build a firewall with a primary and secondary, High-Availability structure. I have configured each of these 2 VirtualBox VMs in GNS3 to connect to each other (for a SYNC) interface, as well as connection to other switches in their topology. These PFsense VMs have about 6 network interfaces in use. I took the configuration file of a single node firewall and am testing with a secondary VM in VirtualBox to get setup as an HA firewall. Pfsync and XML_RPC were set appropriately and tested successfully, as all of the rules of the primary firewall have copied over to the secondary, automatically. I can even create Alias on the primary and they immediately show up on the secondary, so sync is definitely working.

The problem is that all interfaces sync accordingly, except for the interface hosting the VLAN. The secondary VLAN does not pull the firewall rules of the primary pfsense VM automatically like it did for all of the other interfaces. I have even pinged the VLAN IP from each PFsense VM and can verify that there is an established connection between the two interfaces.

Are there any special rules that I am unaware of that might be stopping the synchronization of firewall rules on a interface with a VLAN? I configured a rule on the secondary to all for all connection to be allowed, no luck. Any information would be appreciated.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.