severity 513506 minor retitle 513506 dhcp3-server: Mention new failover peer naming rules in NEWS.Debian / Crash if config doesn't abide to them thanks
In the meanwhile I found the problem and made the config conforming to new naming rules for failover peers of 3.1.x. Since then also the crashes are gone. https://lists.isc.org/pipermail/dhcp-users/2007-September/004538.html describes what went wrong. With 3.0.x peer names only had to be consistent per host. So on stock we had "failover peer ruchen" defined and on ruchen we had "failover peer stock" defined for the same failover connection. Relevant for the right connections were the address parts. 3.1.x allows multiple failover peer connections per IP address, so the name became relevant. I named the failover peer connection the same on both sides and it worked again. So what remains are two minor issues (lowered severity accordingly) with this package: 1) Please mention this quite heavy tripwire in NEWS.Debian for Lenny, because this can hurt others who dist-upgrade from Etch, too. 2) The crash only happens on unexpected input in the dhcpd.conf, so it's at most a minor programming error (which is still present in 3.1.2 btw.) How to reproduce the crash: Host A: failover peer "b" { primary; address a; peer address b; split 128; # only on primary } Host B: failover peer "a" { secondary; address b; peer address a; } Correct configuration not triggering the crash: Host A: failover peer "ab" { primary; address a; peer address b; split 128; # only on primary } Host B: failover peer "ab" { secondary; address b; peer address a; } Kind regards, Axel Beckert -- Axel Beckert <beck...@phys.ethz.ch> support: +41 44 633 26 68 IT Services Group, HPT D 17 voice: +41 44 633 41 89 Departement of Physics, ETH Zurich CH-8093 Zurich, Switzerland http://nic.phys.ethz.ch/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
