'MAC affinity' doing the exact opposite, leading to 'pool churn'?

[Bart Van den Broeck]

I applied the provided patch for extra logging.  At the end, I've included
the logs of the two tests I performed with the patched servers today.  (As
before, the tests where performed on a "fresh install".)  It seems 'client
affinity' is indeed causing the problem.  (BTW, isn't 'client affinity' a
better name than 'MAC address affinity'?)

Kind regards
Bart Van den Broeck
---------------------- ICT-Infrastructuur - Netwerken aka KULeuvenNet --
---------------------- LUDIT - ICTS - K.U.Leuven --


##########
# TEST 1 #
##########
### s1
18:00:46 s1 dhcpd: DHCPDISCOVER from 00:0f:1f:84:ca:f2 via eth1
18:00:47 s1 dhcpd: DHCPOFFER on 134.58.217.140 to 00:0f:1f:84:ca:f2 via eth1
18:00:47 s1 dhcpd: DHCPREQUEST for 134.58.217.140 (134.58.217.231) from 00:0f:1f:84:ca:f2 via eth1
18:00:47 s1 dhcpd: DHCPACK on 134.58.217.140 to 00:0f:1f:84:ca:f2 via eth1
18:03:48 s1 dhcpd: failover: lease 134.58.217.140 given to secondary for client affinity on ack

### s2
18:00:47 s2 dhcpd: DHCPDISCOVER from 00:0f:1f:84:ca:f2 via eth1
18:00:47 s2 dhcpd: DHCPREQUEST for 134.58.217.140 (134.58.217.231) from 00:0f:1f:84:ca:f2 via eth1: lease owned by peer
18:00:48 s2 dhcpd: DHCPOFFER on 134.58.217.141 to 00:0f:1f:84:ca:f2 via eth1


##########
# TEST 2 #
##########
### s1
18:27:04 s1 dhcpd: DHCPDISCOVER from 00:0f:1f:84:ca:f2 via eth1
18:27:05 s1 dhcpd: DHCPOFFER on 134.58.217.140 to 00:0f:1f:84:ca:f2 via eth1
18:27:05 s1 dhcpd: DHCPREQUEST for 134.58.217.140 (134.58.217.231) from 00:0f:1f:84:ca:f2 via eth1
18:27:05 s1 dhcpd: DHCPACK on 134.58.217.140 to 00:0f:1f:84:ca:f2 via eth1
18:27:06 s1 dhcpd: DHCPREQUEST for 134.58.217.140 (134.58.217.231) from 00:0f:1f:84:ca:f2 via eth1
18:27:06 s1 dhcpd: DHCPACK on 134.58.217.140 to 00:0f:1f:84:ca:f2 via eth1
18:33:08 s1 dhcpd: failover: lease 134.58.217.140 given to secondary for client affinity on ack

### s2
18:27:05 s2 dhcpd: DHCPDISCOVER from 00:0f:1f:84:ca:f2 via eth1: load balance to peer dhcp-failover
18:27:05 s2 dhcpd: DHCPREQUEST for 134.58.217.140 (134.58.217.231) from 00:0f:1f:84:ca:f2 via eth1: lease owned by peer
18:27:07 s2 dhcpd: DHCPREQUEST for 134.58.217.140 (134.58.217.231) from 00:0f:1f:84:ca:f2 via eth1
18:27:07 s2 dhcpd: DHCPACK on 134.58.217.140 to 00:0f:1f:84:ca:f2 via eth1

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm