> On Mar 24, 2015, at 9:47 AM, Steve Yates <[email protected]> wrote: > > I'm going to start a new thread since I think this is a different issue. > > I have a rule to allow all IPv4 from PFSYNC net to PFSYNC net. That > network is on a VLAN with only those two interfaces on it. > > The failover and fail back works fine on all five CARP > interfaces/aliases if router1 is shut down, it enters CARP maintenance mode, > etc. > > I think this is a bug that if the CARP skew setting syncs, something > happens to the backup so it has a blank Status and no longer considers itself > the Backup for that interface, and therefore failover does not happen. > (enabling CARP maintenance mode on router1 sets only the other four > interfaces to Backup status and the broken one remains Master). > > Interesting to note, the breakage happens immediately upon editing the > router1 skew, before Apply Changes are clicked on router1. And, when > router2's CARP alias is in that state, setting the skew on router1 back to 0 > does not sync over to router2; its skew stays at 101. It's as if the link is > broken. >
Since nobody else has chimed in are you sure CARP setting changes are supposed to be synced? It makes sense that when a primary syncs to a new secondary, or a new VIP is created on the Master, defaults are chosen on the secondary to ensure it comes up as Backup. After that happens, I don’t think I want changes to CARP settings to be synced. What are you doing messing around with base and skew anyway? _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
