<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Thanks for reply.<br><br>My setup is like this : <br> eth1<br> Windows 2003 server ( 192.168.9.2/23)-------------------(192.168.8.177/23) Linux PC(Relay) (22.214.171.124/24----------eth0----Windows XP Client ( DHCP
client getting IP 126.96.36.199/24)<br><br>In windows server the default gw is 192.168.8.177. The DHCP pool configured gateway is 188.8.131.52 ( relay agent ip) <br><br>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 184.108.40.206 . <br><br>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. <br><br>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 ?<br><br>Please let me know your observations, after seeing the captures. I have tried many times with similar
observation.<br><br>Regards,<br>Sujata<br> <br>--- On <b>Wed, 4/18/12, Simon Hobson <i><email@example.com></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Simon Hobson <firstname.lastname@example.org><br>Subject: Re: DHCP Relay: Duplicate packets for DHCPRELEASE and DHCPREQUEST<br>To: "Users of ISC DHCP" <email@example.com><br>Date: Wednesday, April 18, 2012, 2:38 PM<br><br><div class="plainMail">Sujata Verma wrote:<br><br>> I am using dhcp-4.2.2rc1. I have started the dhcp relay with options<br>> <br>> dhcrelay -d -i eth0 -i eth1 serverip<br>> <br>> 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.<br>> <br>> 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.<br>> <br>> Is this normal behavior? The same is observed with unicast DHCPREQUEST .<br><br>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.<br><br>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 ?<br><br>-- Simon Hobson<br><br>Visit <a href="http://www.magpiesnestpublishing.co.uk/"
target="_blank">http://www.magpiesnestpublishing.co.uk/</a> for books by acclaimed<br>author Gladys Hobson. Novels - poetry - short stories - ideal as<br>Christmas stocking fillers. Some available as e-books.<br>_______________________________________________<br>dhcp-users mailing list<br><a ymailto="mailto:firstname.lastname@example.org" href="/email@example.com">firstname.lastname@example.org</a><br><a href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br></div></blockquote></td></tr></table>