<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Thanks for your reply . We cannot run the command giving only one interface , either it has to be all or none. So it can be like <br><br><span style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;">dhcrelay –d 192.168.9.2</span><br><br>or <br><br><span style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;">dhcrelay –d –i eth0 -i eth1 192.168.9.2</span><br><br>If we give only one interface it will silently discard the packet. I have tested it.<br><br>Please see below bug for more information.<br><br>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648401<br><br>Regards,<br>Sujata<br><br>--- On <b>Wed, 4/18/12, arunprasad <i><arunprasad@pointred.co></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: arunprasad
<arunprasad@pointred.co><br>Subject: RE: DHCP Relay: Duplicate packets for DHCPRELEASE and DHCPREQUEST<br>To: "'Users of ISC DHCP'" <dhcp-users@lists.isc.org><br>Date: Wednesday, April 18, 2012, 10:47 PM<br><br><div id="yiv904071049"><style><!--
#yiv904071049
_filtered #yiv904071049 {font-family:Shruti;panose-1:2 11 5 2 4 2 4 2 2 3;}
_filtered #yiv904071049 {font-family:Shruti;panose-1:2 11 5 2 4 2 4 2 2 3;}
_filtered #yiv904071049 {font-family:Cambria;panose-1:2 4 5 3 5 4 6 3 2 4;}
_filtered #yiv904071049 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}
_filtered #yiv904071049 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}
#yiv904071049
#yiv904071049 p.yiv904071049MsoNormal, #yiv904071049 li.yiv904071049MsoNormal, #yiv904071049 div.yiv904071049MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"serif";}
#yiv904071049 a:link, #yiv904071049 span.yiv904071049MsoHyperlink
{color:blue;text-decoration:underline;}
#yiv904071049 a:visited, #yiv904071049 span.yiv904071049MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
#yiv904071049 p.yiv904071049MsoAcetate, #yiv904071049 li.yiv904071049MsoAcetate, #yiv904071049 div.yiv904071049MsoAcetate
{margin:0in;margin-bottom:.0001pt;font-size:8.0pt;font-family:"sans-serif";}
#yiv904071049 span.yiv904071049EmailStyle17
{font-family:"sans-serif";color:#1F497D;}
#yiv904071049 span.yiv904071049BalloonTextChar
{font-family:"sans-serif";}
#yiv904071049 span.yiv904071049EmailStyle20
{font-family:"sans-serif";color:#1F497D;}
#yiv904071049 .yiv904071049MsoChpDefault
{font-size:10.0pt;}
_filtered #yiv904071049 {margin:1.0in 1.0in 1.0in 1.0in;}
#yiv904071049 div.yiv904071049WordSection1
{}
--></style><div><div class="yiv904071049WordSection1"><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;">Use this command:-</span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;"> </span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;">dhcrelay –d –i eth0 192.168.9.2</span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;"> </span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;">ensure that from </span><span style="font-size:11.0pt;font-family:"serif";color:#376092;">80.1.1.1/24 your DHCP-Server is reachable (vice versa). </span></p><p class="yiv904071049MsoNormal"><span
style="font-size:11.0pt;font-family:"serif";color:#376092;"> </span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"serif";color:#376092;">Regards</span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"serif";color:#376092;">Arun.</span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;"> </span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;"> </span></p><div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in;"><p class="yiv904071049MsoNormal"><b><span style="font-size:10.0pt;font-family:"sans-serif";">From:</span></b><span style="font-size:10.0pt;font-family:"sans-serif";"> arunprasad [mailto:arunprasad@pointred.co] <br><b>Sent:</b> Wednesday, April 18, 2012
10:05 PM<br><b>To:</b> 'Users of ISC DHCP'<br><b>Subject:</b> RE: DHCP Relay: Duplicate packets for DHCPRELEASE and DHCPREQUEST</span></p></div></div><p class="yiv904071049MsoNormal"> </p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"serif";color:#376092;">Hi Sujata,</span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"serif";color:#376092;"> </span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"serif";color:#376092;">dhcrelay -d -i eth0 -i eth1 serverip </span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"serif";color:#376092;"> </span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"serif";color:#376092;">-i ifname </span></p><p class="yiv904071049MsoNormal"><span
style="font-size:11.0pt;font-family:"serif";color:#376092;">Listen for DHCPv4/BOOTP queries on interface ifname. Multiple interfaces may be specified by using more than one -i option. If no interfaces are specified on the command line, dhcrelay will identify all network interfaces, eliminating non-broadcast interfaces if possible, and attempt to listen on all of them. </span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"serif";color:#376092;"> </span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"serif";color:#376092;">So try running dhrelay on your downstream interface only i.e.. 80.1.1.1/24 interface.</span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"serif";color:#376092;"> </span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"serif";color:#376092;">PS:- IP
Forwarding needs to enable. If your setup is as below.</span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"serif";color:#376092;"> </span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"serif";color:#376092;">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) </span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"serif";color:#376092;"> </span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"serif";color:#376092;">Regards</span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"serif";color:#376092;">Arun.</span></p><p class="yiv904071049MsoNormal"> </p><p class="yiv904071049MsoNormal"> </p><p
class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;"> </span></p><p class="yiv904071049MsoNormal"><span style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;"> </span></p><p class="yiv904071049MsoNormal"><b><span style="font-size:10.0pt;font-family:"sans-serif";">From:</span></b><span style="font-size:10.0pt;font-family:"sans-serif";"> dhcp-users-bounces+arunprasad=pointred.co@lists.isc.org [mailto:dhcp-users-bounces+arunprasad=pointred.co@lists.isc.org] <b>On Behalf Of </b>Sujata Verma<br><b>Sent:</b> Wednesday, April 18, 2012 6:36 PM<br><b>To:</b> Users of ISC DHCP<br><b>Subject:</b> Re: DHCP Relay: Duplicate packets for DHCPRELEASE and DHCPREQUEST</span></p><p class="yiv904071049MsoNormal"> </p><table class="yiv904071049MsoNormalTable" border="0" cellpadding="0" cellspacing="0"><tbody><tr><td style="padding:0in 0in 0in 0in;"
valign="top"><p class="yiv904071049MsoNormal"><br>Thanks for the reply. <br><br>Yes, it is duplicating the unicast DHCPREQUEST packets as well. <br><br>So is it a bug, is there anything i can do to stop doing it ( in code ) , any pointers? <br><br>@Arun,<br><br>There is no switch in between, the setup to be precise is <br><br><br>Win Server-----------cross cable--------------Linux PC------------hub-------Win XP client<br>192.168.9.1/24 192.168.9.2/24 10.1.1.2/8 10.1.1.3/8 ( from server)<br><br>I changed the subnet as above but same behavior.<br><br><br>One more observation : <br><br>if i disable ip_forward flag , the DHCP relay agent is sending only one DHCPRELEASE packet with correct giaddr ( incoming eth0 interface ).
But as forwarding is disabled it is understood that the client DHCPRELEASE message is not forwarded to the server but why the other "eth1" interface DHCPRELEASE message is not being generated from relay agent? <br><br>Any pointers? <br><br>Regards,<br>Sujata<br><br><br><br><br>--- On <b>Wed, 4/18/12, Simon Hobson <i><<a rel="nofollow" ymailto="mailto:dhcp1@thehobsons.co.uk" target="_blank" href="/mc/compose?to=dhcp1@thehobsons.co.uk">dhcp1@thehobsons.co.uk</a>></i></b> wrote:</p><p class="yiv904071049MsoNormal" style="margin-bottom:12.0pt;"><br>From: Simon Hobson <<a rel="nofollow" ymailto="mailto:dhcp1@thehobsons.co.uk" target="_blank" href="/mc/compose?to=dhcp1@thehobsons.co.uk">dhcp1@thehobsons.co.uk</a>><br>Subject: Re: DHCP Relay: Duplicate packets for DHCPRELEASE and DHCPREQUEST<br>To: "Users of ISC DHCP" <<a rel="nofollow" ymailto="mailto:dhcp-users@lists.isc.org" target="_blank"
href="/mc/compose?to=dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a>><br>Date: Wednesday, April 18, 2012, 5:21 PM</p><div><p class="yiv904071049MsoNormal">Sujata Verma wrote:<br><br>> My setup is like this : eth1<br>> 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)<br><br>That's better<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 80.1.1.1 .<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>My guess (I've not actually used the ISC relay) is that it's sniffing the packets and picking up the unicast packet from the client to the server both when it enters the relay on eth0 and when it exits via eth1. That, to my understanding, is wrong.<br><br>It would be interesting to see what happens to a unicast DHCP-Request packet ? The Request packet in your captures is a broadcast packet which is being relayed by the Relay Agent (correctly). You will need to (temporarily) tweak your server config down to a short lease time so that the client will renew in a timescale that's workable.<br>Based on the above, I suspect you'll see those packets duplicated as well.<br><br>-- Simon
Hobson<br><br>Visit <a rel="nofollow" target="_blank" href="http://www.magpiesnestpublishing.co.uk/">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 rel="nofollow">dhcp-users@lists.isc.org</a><br><a rel="nofollow" target="_blank" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a></p></div></td></tr></tbody></table><p class="yiv904071049MsoNormal"><span style="font-size:10.0pt;font-family:"sans-serif";"> </span></p></div></div>
<pre>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.
</pre></div><br>-----Inline Attachment Follows-----<br><br><div class="plainMail">_______________________________________________<br>dhcp-users mailing list<br><a ymailto="mailto:dhcp-users@lists.isc.org" href="/mc/compose?to=dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br><a href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a></div></blockquote></td></tr></table>