Multiple dhcrelay setup causing multiple duplicate DHCP requests

Mon Aug 16 04:51:19 UTC 2010

Glad to know I'm not the only one affected.
It does make DHCPD redundancy unusable as the logging partition fills up
and makes using the logs for troubleshooting impossible.
Any suggestions on how to work-around this issue or get it patched?

Cheers

Mike Hodgkinson
Support & Managed Services
Solnet Solutions Limited
Level 12, Solnet House
70 The Terrace, Wellington 6011, New Zealand
PO Box 397, Wellington 6140, New Zealand
DDI +64 4 462 5064, Mobile +64 21 754 339
Main +64 4 462 5000, Fax +64 4 462 5012

www.solnetsolutions.co.nz
A Solnet Group Company

  From:       budiw at rootbox.or.id                                                                               

  To:         "Users of ISC DHCP" <dhcp-users at lists.isc.org>                                                    

  Date:       15/08/2010 09:39                                                                                  

  Subject:    Re: Multiple dhcrelay setup causing multiple duplicate DHCP requests                              

  Sent by:    dhcp-users-bounces+michael.hodgkinson=solnetsolutions.co.nz at lists.isc.org                         

>
>
> Hi guys,
>
> I need some assistance with a multiple dhcrelay setup with failover dhcpd
> servers.
> The problem I'm getting is multiple duplicate dhcp requests being
received
> by the dhcpd servers (which is filling up the disk very quickly on the
> server).
>
> Here is the log from one of the dhcp servers showing the result:
> Jul 30 11:56:31 alns0 dhcpd: DHCPREQUEST for 10.1.70.185 from
> 00:0c:29:42:f1:1b via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPACK on 10.1.70.185 to 00:0c:29:42:f1:1b
> via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPREQUEST for 10.1.70.185 from
> 00:0c:29:42:f1:1b via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPACK on 10.1.70.185 to 00:0c:29:42:f1:1b
> via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPREQUEST for 10.1.70.185 from
> 00:0c:29:42:f1:1b via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPACK on 10.1.70.185 to 00:0c:29:42:f1:1b
> via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPREQUEST for 10.1.70.185 from
> 00:0c:29:42:f1:1b via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPACK on 10.1.70.185 to 00:0c:29:42:f1:1b
> via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPREQUEST for 10.1.70.185 from
> 00:0c:29:42:f1:1b via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPACK on 10.1.70.185 to 00:0c:29:42:f1:1b
> via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPREQUEST for 10.1.70.185 from
> 00:0c:29:42:f1:1b via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPACK on 10.1.70.185 to 00:0c:29:42:f1:1b
> via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPREQUEST for 10.1.70.185 from
> 00:0c:29:42:f1:1b via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPACK on 10.1.70.185 to 00:0c:29:42:f1:1b
> via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPREQUEST for 10.1.70.185 from
> 00:0c:29:42:f1:1b via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPACK on 10.1.70.185 to 00:0c:29:42:f1:1b
> via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPREQUEST for 10.1.70.185 from
> 00:0c:29:42:f1:1b via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPACK on 10.1.70.185 to 00:0c:29:42:f1:1b
> via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPREQUEST for 10.1.70.185 from
> 00:0c:29:42:f1:1b via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPACK on 10.1.70.185 to 00:0c:29:42:f1:1b
> via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPREQUEST for 10.1.70.185 from
> 00:0c:29:42:f1:1b via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPACK on 10.1.70.185 to 00:0c:29:42:f1:1b
> via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPREQUEST for 10.1.70.185 from
> 00:0c:29:42:f1:1b via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPACK on 10.1.70.185 to 00:0c:29:42:f1:1b
> via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPREQUEST for 10.1.70.185 from
> 00:0c:29:42:f1:1b via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPACK on 10.1.70.185 to 00:0c:29:42:f1:1b
> via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPREQUEST for 10.1.70.185 from
> 00:0c:29:42:f1:1b via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPACK on 10.1.70.185 to 00:0c:29:42:f1:1b
> via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPREQUEST for 10.1.70.185 from
> 00:0c:29:42:f1:1b via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPACK on 10.1.70.185 to 00:0c:29:42:f1:1b
> via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPREQUEST for 10.1.70.185 from
> 00:0c:29:42:f1:1b via 10.1.70.1
> Jul 30 11:56:31 alns0 dhcpd: DHCPACK on 10.1.70.185 to 00:0c:29:42:f1:1b
> via 10.1.70.1
>
> The network is configured like this:
>
>   [ dhcpd1 ]
>        |
>  eth0/vlan120
> [ fw1/dhcrelay ]
>      eth5
>        |
>      eth5
> [ fw2/dhcrelay ]
>  eth0/vlan120
>        |
>    [ dhcpd2 ]
>
> The configuration on the dhcrelays is like this:
>
> /usr/sbin/dhcrelay3 -q -i eth0 -i eth1 -i vlan1 -i vlan120 -i vlan140 -i
> vlan150 -i vlan151 -i vlan170 dhcpd1 dhcpd2 (actually have IPs in here)
>

I'm having same situation. On my dhcpd servers showed logs like this.
Except, the ip's is from all the dhcrelay (I have 6 dhcrelay).
Other than some logs that get bigger and bigger, there's no another effect
I presume. CMIIW.

_______________________________________________
dhcp-users mailing list
dhcp-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users

Attention:
This email may contain information intended for the sole use of
the original recipient. Please respect this when sharing or
disclosing this email's contents with any third party. If you
believe you have received this email in error, please delete it
and notify the sender or postmaster at solnetsolutions.co.nz as
soon as possible. The content of this email does not necessarily
reflect the views of Solnet Solutions Ltd.