DHCP Relay: Duplicate packets for DHCPRELEASE and DHCPREQUEST

Wed Apr 18 11:11:58 UTC 2012

If setup is  connected in L2-Switch, use VLAN, ensure client broadcast
messages should not hit directly to server. 

Regards

Arun.

From: arunprasad [mailto:arunprasad at pointred.co] 
Sent: Wednesday, April 18, 2012 4:35 PM
To: 'Users of ISC DHCP'
Subject: RE: DHCP Relay: Duplicate packets for DHCPRELEASE and DHCPREQUEST

Hi Sujitha,

Try keeping DHCP-Server & DHCP-relay in different subnet.

Regards

Arun.

From: dhcp-users-bounces+arunprasad=pointred.co at lists.isc.org
[mailto:dhcp-users-bounces+arunprasad=pointred.co at lists.isc.org] On Behalf
Of Sujata Verma
Sent: Wednesday, April 18, 2012 4:16 PM
To: Users of ISC DHCP
Subject: Re: DHCP Relay: Duplicate packets for DHCPRELEASE and DHCPREQUEST

Thanks for reply.

My setup is like this :                                         
                                                                      eth1
  Windows 2003 server ( 192.168.9.2/23)-------------------(192.168.8.177/23)
Linux PC(Relay) (80.1.1.1/24----------eth0----Windows XP Client ( DHCP
client getting IP 80.1.1.2/24)

In windows server the default gw is 192.168.8.177. The DHCP pool configured
gateway is 80.1.1.1 ( relay agent ip) 

I am attaching the wireshark capture for both client and server. In this we
can see that the DHCPDISCOVER is only being sent once to the server which
relay is forwarding while adding giaddr field as 80.1.1.1 . 

When DHCPRELEASE packet is being sent, it is sent directly to the server and
with other two packets as duplicates with giaddr as of two interfaces. 

In linux pc i have only enabled ipv4_forward and disabled iptables
completely. Is there any other configuration which can result in my
observation like this ?

Please let me know your observations, after seeing the captures. I have
tried many times with similar observation.

Regards,
Sujata

--- On Wed, 4/18/12, Simon Hobson <dhcp1 at thehobsons.co.uk> wrote:

From: Simon Hobson <dhcp1 at thehobsons.co.uk>
Subject: Re: DHCP Relay: Duplicate packets for DHCPRELEASE and DHCPREQUEST
To: "Users of ISC DHCP" <dhcp-users at lists.isc.org>
Date: Wednesday, April 18, 2012, 2:38 PM

Sujata Verma wrote:

> I am using dhcp-4.2.2rc1. I have started the dhcp relay with options
> 
> dhcrelay -d -i eth0 -i eth1 serverip
> 
> everything is working fine except that when client release the ip and send
DHCPRELEASE packet on server side i get 3 packets for each DHCPRELEASE.
> 
> One is directly sent to server ( which is valid packet) the other two are
duplicate of this packet which is generated by relay agent with giaddr as
address of eth0 and eth1 interface.
> 
> Is this normal behavior? The same is observed with unicast DHCPREQUEST .

Are you sure about the unicast packets ? On a switched network, the packet
should only ever bee seen by the server - it shouldn't reach the relay
agent.

For any boradcast packets, I'd expect to see two copies - one picked up
directly by the server, and one picked up by the relay agent. This is
inherent in the way the relay agent needs (due to the way it's built) to
listen on both interfaces. I wouldn't expect to see a packet with the
relay's eth1 address in it - they aren't connected to the same network are
they ?

-- Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.
_______________________________________________
dhcp-users mailing list
dhcp-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users

DISCLAIMER:
The information contained in this message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and permanently delete this message and any attachments from your system. Any dissemination, use, review, distribution, printing or copying of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. PointRed Telecom Ltd (including its group companies) shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system and does not guarantee that the integrity of this communication has been maintained or that this communication is free of viruses, interceptions or interferences. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20120418/4c734c0b/attachment-0001.html>