Bug #3211
closed
DHCP failover configuration not working in 2.1-RELEASE
0%
Description
Both nodes are getting setup as Primary.
While 2.1 was in RC a similar problem where both nodes were getting setup as secondary was fixed by this commit: https://github.com/pfsense/pfsense/commit/24670866827b4e2d7a4a05baaf6d09ee377ce7cb . Did that commit not make it in the release?
I can probably fix this. Do you want me to just send a pull request in github with the fix?
Shahid
Updated by Chris Buechler about 11 years ago
- Status changed from New to Rejected
DHCP failover is definitely working in general in 2.1 release. We have it running in 5 networks, and have tested it on multiple customer networks. The linked commit is part of what fixed it being broken in earlier 2.1 snapshots and is in 2.1 release. Post info to the forum or mailing list if you're having trouble on release with specifics.
Updated by Shahid Sheikh about 11 years ago
Chris,
I upgraded 6 firewalls to 2.1-RELEASE and it is indeed broken on all 6 of them.
The foreach loop on line 453 of services.inc assumes that the backup/secondary node will never have any CARP VIPs with advskew <20 which is a bad assumption to make.
All of my more complicated setups have VIPs on the backup node that are unique to just that node and have a advskew of <20.
I can get around the problem by increasing the advskew on the VIPs of the backup node.
CARP VIPs and DHCPd are unrelated and one should not be used to determine the configuration of the other. Simply give the enduser the option to select which is the primary and which is the secondary node.
Thanks,
Shahid
Updated by Doktor Notor about 11 years ago
And on another note, the referenced commit got reverted here: https://github.com/pfsense/pfsense/commit/a3d6166bb20a3ff4d6a7ff57290c3e59ce51ded4/