Hi, On Fri, Mar 01, 2013 at 02:12:11PM +1100, Jerome Alet wrote: > > We've just upgraded our two-nodes failover cluster to "2.1BETA1 built on > Thu Feb 28 04:29:38 EST 2013", because we encountered problems with DHCP > failover not being in state "normal" / "normal" for some interfaces. > > Searching the web, I've found this link which might be related : > > http://redmine.pfsense.org/issues/1730 > > When trying to find filter rules matching ports 519 or 520 in > /tmp/rules.debug as described in this bug report, there's no match at > all. > > As far as I understand the answer to this bug report, the required rules > should be automatically added. > > Is this to be expected or is there a problem somewhere ?
I've just found and fixed one part of our problem : It happens that DHCP was activated on a interface for testing purpose. When it was deactivated when testing was finished, the assigned range wasn't reset to an empty set by the WebUI, and in the config.xml file available from a backup I saw the range still being defined despite DHCP being disabled on this interface. Then I went to the WebUI, checked the "Enable DHCP on XX interface", then manually emptied the range, then unchecked the "Enable DHCP on XX interface" and finally clicked the "Save" button. Immediately DHCP sync worked and all interfaces were in "normal" / "normal" again. We've still got a sync problem when activating/deactivating failover peer ip for one interface, but I suppose the problem is similar and I'll look into this ASAP. Hoping this will help other people in the same situation. bye -- Jérôme Alet - <[email protected]> - Direction du Système d'Information Université de la Nouvelle-Calédonie - BPR4 - 98851 NOUMEA CEDEX Tél : +687 290081 Fax : +687 254829 _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
