Multiple DHCPREQUEST/DHCPACK logged for a single DHCPtransaction. Anyone seen this before?

[Randall C Grimshaw]

We saw this when some switches were mis-configured with dhcp server
information. I won't go into detail on why we were testing this, but
setting the dhcp server value in the wrong context will result in the
switch acting as a bootphelper relay in addition to the router. The
result is an unneccessary magnification of dhcp traffic.
.

-----Original Message-----
From: dhcp-users-bounce at isc.org [mailto:dhcp-users-bounce at isc.org] On
Behalf Of Steve van der Burg
Sent: Friday, November 16, 2007 8:57 AM
To: dhcp-users at isc.org
Subject: Multiple DHCPREQUEST/DHCPACK logged for a single
DHCPtransaction. Anyone seen this before?

Does anyone know if this indicates that my network is messed up somehow?
Servers are a partner pair running ISC DHCPd 3.0.5.  Network is quite
large, and I don't run or configure it.  I've always wondered about the
two incoming gateway(?) addresses on the requests (.250 and .251).  Our
official router gateways are all .254.

Is this at all normal?  These entries have been edited to remove the
server name and log facility, but are otherwise posted intact:

Nov 16 08:42:27 dhcpd: DHCPREQUEST for 10.136.76.177 from
00:1a:4b:39:11:54 (ABC123) via 10.136.76.250
Nov 16 08:42:27 dhcpd: DHCPACK on 10.136.76.177 to 00:1a:4b:39:11:54
(ABC123) via 10.136.76.250
Nov 16 08:42:27 dhcpd: DHCPREQUEST for 10.136.76.177 from
00:1a:4b:39:11:54 (ABC123) via 10.136.76.251
Nov 16 08:42:27 dhcpd: DHCPACK on 10.136.76.177 to 00:1a:4b:39:11:54
(ABC123) via 10.136.76.251
Nov 16 08:42:27 dhcpd: DHCPREQUEST for 10.136.76.177 from
00:1a:4b:39:11:54 (ABC123) via 10.136.76.250
Nov 16 08:42:27 dhcpd: DHCPACK on 10.136.76.177 to 00:1a:4b:39:11:54
(ABC123) via 10.136.76.250
Nov 16 08:42:27 dhcpd: DHCPREQUEST for 10.136.76.177 from
00:1a:4b:39:11:54 (ABC123) via 10.136.76.251
Nov 16 08:42:27 dhcpd: DHCPACK on 10.136.76.177 to 00:1a:4b:39:11:54
(ABC123) via 10.136.76.251
Nov 16 08:42:29 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:29 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:29 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:29 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:30 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:30 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:31 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:31 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:33 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:33 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:37 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:37 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:45 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:45 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:46 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:46 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:46 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:42:46 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:43:30 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0
Nov 16 08:43:30 dhcpd: DHCPACK to 10.136.76.177 (00:1a:4b:39:11:54) via
eri0

Thanks.

...Steve

-- 

Steve van der Burg
Information Management
London Health Sciences Centre
& St. Joseph's Health Care London
(519) 685-8500 ext 35559
steve.vanderburg at lhsc.on.ca

 
------------------------------------------------------------------------
--------
This information is directed in confidence solely to the person named
above and may contain confidential and/or privileged material. This
information may not otherwise be distributed, copied or disclosed. If
you have received this e-mail in error, please notify the sender
immediately via a return e-mail and destroy original message. Thank you
for your cooperation.