Bus error / Segmenation fault dhcpd-4.2.4-P1

[Jeroen Louwes]

Hi,


I have some troubles getting failover working on dhcpd. Im running the
latest 4.2.4-P1 version on a mips platform (OpenWRT).

As soon as i enable failover in the configuration, dhcpd is unable to
start and exits after 4-5 seconds with a "Segmentation fault" or "Bus
error". Without the failover statements, dhcpd starts fine. What am i
doing wrong?


root at mercurius:~# /usr/sbin/dhcpd -d -cf /etc/dhcpd.conf -lf
/var/dhcpd.leases -pf /var/run/dhcpd.pid br-lan
Internet Systems Consortium DHCP Server 4.2.4-P1
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Wrote 0 leases to leases file.
Listening on LPF/br-lan/c4:3d:c7:86:0a:9a/192.168.33.0/24
Sending on   LPF/br-lan/c4:3d:c7:86:0a:9a/192.168.33.0/24
Sending on   Socket/fallback/fallback-net
failover peer dhcp-failover: I move from recover to startup
Bus error

root at mercurius:~# /usr/sbin/dhcpd -d -cf /etc/dhcpd.conf -lf
/var/dhcpd.leases -pf /var/run/dhcpd.pid br-lan
Internet Systems Consortium DHCP Server 4.2.4-P1
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Wrote 0 leases to leases file.
Listening on LPF/br-lan/c4:3d:c7:86:0a:9a/192.168.33.0/24
Sending on   LPF/br-lan/c4:3d:c7:86:0a:9a/192.168.33.0/24
Sending on   Socket/fallback/fallback-net
failover peer dhcp-failover: I move from recover to startup
Segmentation fault


Here is my configuration:

ddns-update-style interim;
ddns-domainname "louwes.info.";

include "/etc/rndc.key";

zone louwes.info. {
	primary 127.0.0.1;
	key rndc-key;
}

option domain-name "louwes.info";
option domain-name-servers 192.168.33.2, 192.168.33.3;
default-lease-time 86400;
max-lease-time 172800;
authoritative;

key primaryserver {
	algorithm hmac-md5;
	secret "verysupersecretkey";
};

omapi-key primaryserver;
omapi-port 7911;

failover peer "dhcp-failover" {
	primary;
	address 192.168.33.2;
	port 519;
	peer address 192.168.33.3;
	peer port 520;
	max-response-delay 60;
	max-unacked-updates 10;
	mclt 1800;
	split 128;
	load balance max seconds 3;
}

subnet 192.168.33.0 netmask 255.255.255.0 {
	pool {
		failover peer "dhcp-failover";
		range 192.168.33.101 192.168.33.199;
		option routers 192.168.33.1;
		option ntp-servers 192.168.33.2, 192.168.33.3;
	}		

	zone 33.168.192.in-addr.arpa. {
		primary 127.0.0.1;
		key rndc-key;
	}
}


Thank you for your time !


Kind regards,
Jeroen Louwes.