the question about the dhcp relay deployment

Derek Wang xiangshu129 at gmail.com
Mon May 9 13:46:29 UTC 2011


On Mon, May 9, 2011 at 8:00 PM, <dhcp-users-request at lists.isc.org> wrote:

> Send dhcp-users mailing list submissions to
>        dhcp-users at lists.isc.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://lists.isc.org/mailman/listinfo/dhcp-users
> or, via email, send a message with subject or body 'help' to
>        dhcp-users-request at lists.isc.org
>
> You can reach the person managing the list at
>        dhcp-users-owner at lists.isc.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of dhcp-users digest..."
>
>
> Today's Topics:
>
>   1. Re: Insert delay in dhcp3-relay ? (Benjamin)
>   2. Re: dhcp-users Digest, Vol 31, Issue 16 (Derek Wang)
>   3. Re: dhcp-users Digest, Vol 31, Issue 16 (Derek Wang)
>   4. Re: the question about the dhcp relay deployment (Simon Hobson)
>   5. Convite para conectar-se no LinkedIn
>      (Eduardo Henrique De Oliveira Gon?alves)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 08 May 2011 18:06:18 +0200
> From: Benjamin <hexor38 at gmail.com>
> Subject: Re: Insert delay in dhcp3-relay ?
> To: dhcp-users at lists.isc.org
> Message-ID: <4DC6BF7A.7060205 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Le 05/05/2011 09:05, dhcp-users-request at lists.isc.org a ?crit :
> > You may care to look at the min-secs statement. Adding this to the
> > subnet declaration for the 'remote' subnet on each server should
> > achieve what you want.
> >
> >          The min-secs statement
> >
> >             min-secs seconds;
> >
> >             Seconds should be the minimum number of seconds since a
> client began
> >             trying to acquire a new lease before the DHCP server will
> respond to
> >             its  request.   The  number  of  seconds is based on what the
> client
> >             reports, and the maximum value that the client  can  report
>  is  255
> >             seconds.    Generally,  setting  this to one will result in
> the DHCP
> >             server not responding to the  client's  first  request,  but
>  always
> >             responding to its second request.
> >
> >             This  can  be  used  to  set  up a secondary DHCP server
> which never
> >             offers an address to a client until  the  primary  server
>  has  been
> >             given a chance to do so.   If the primary server is down, the
> client
> >             will bind to the secondary  server,  but  otherwise  clients
>  should
> >             always  bind  to  the primary.   Note that this does not, by
> itself,
> >             permit a primary server and a secondary server to share  a
>  pool  of
> >             dynamically-allocatable addresses.
> >
> > -- Simon Hobson
> Hello,
> This is the function I need ! but ... I have test it, and it don't work,
> I put the min-secs in my range but the DHCP send an offer without delay
> (min-secs delay).
> Have you got an idea  why the delay don't work ? ( I have tested out of
> the range (at the start of dhcpd.conf) but it's the same result...)
>
> Thanks.
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 9 May 2011 09:29:38 +0800
> From: Derek Wang <xiangshu129 at gmail.com>
> Subject: Re: dhcp-users Digest, Vol 31, Issue 16
> To: dhcp-users at lists.isc.org
> Message-ID: <BANLkTi=hoedQiWFbGTkb37kKtNUCm+JefQ at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I got the points!
>
> Thanks for all your explanations and help!
>
> --
> Best Regards,
> Derek Wang
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.isc.org/pipermail/dhcp-users/attachments/20110509/e5ea93b6/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Mon, 9 May 2011 13:14:05 +0800
> From: Derek Wang <xiangshu129 at gmail.com>
> Subject: Re: dhcp-users Digest, Vol 31, Issue 16
> To: dhcp-users at lists.isc.org
> Message-ID: <BANLkTikXCi67eJpvNGbO7cv6ExGDC33Qrg at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Simon, you mentioned in last paragraph that we also need to make sure the
> client can contact the server via unicast after
> got the IP in the client side, it's right because the client need to send
> the DHCPREQUEST packet to the dhcp server to renew
> the information.
>
> But If the client can not contact dhcp server via unicast, like without
> correct route info, then what will happen?
> I think the client will time out after the max-lease-time, then the client
> will initiate the DHCPDISCOVER again,
> and the relay will do the left work like before. But I tried that in
> Solaris, the result is not like what I assume. Actually
> the server side see the DHCPDISCOVER packet, but the server will not return
> the DHCPOFFER to the relay, then to
> the client. And when I return to check the client's expire info, and the
> result is 1969 Wed Dec 31 23:59:59 1969, but the
> output is 2011 Mon May 09 04:53:23 2011 after the client get the dhcp info
> successfully first time. It's so weird. Is that
> expected?
>
> thanks!
> --
> Best Regards,
> Derek Wang
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.isc.org/pipermail/dhcp-users/attachments/20110509/069da6e1/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 4
> Date: Mon, 9 May 2011 07:51:51 +0100
> From: Simon Hobson <dhcp1 at thehobsons.co.uk>
> Subject: Re: the question about the dhcp relay deployment
> To: Users of ISC DHCP <dhcp-users at lists.isc.org>
> Message-ID: <p0624081bc9ed3d9eaea9 at simon.thehobsons.co.uk>
> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
>
> Derek Wang wrote:
>
> Can you please maintain the thread subject ? When people come back to
> look through the archives, "dhcp-users Digest, Vol 31, Issue 16" will
> mean nothing at all.
>
> >Simon, you mentioned in last paragraph that we also need to make
> >sure the client can contact the server via unicast after
> >got the IP in the client side, it's right because the client need to
> >send the DHCPREQUEST packet to the dhcp server to renew
> >the information.
> >
> >But If the client can not contact dhcp server via unicast, like
> >without correct route info, then what will happen?
> >I think the client will time out after the max-lease-time, then the
> >client will initiate the DHCPDISCOVER again,
>
> The normal process is that after about half the lease time, the
> client should start unicasting renewal requests to the server that
> issued the lease. Towards the end of the lease, but before it's
> expired, is should switch to broadcasting renewal requests - which
> means any server can respond. Finally, if nothing has responded to
> the renewal request (either by unicast, then later by broadcast), the
> client will deconfigure the interface and start from the beginning
> and broadcast discover packets.
>
> I would suggest you track down the book "The DHCP Handbook" by Ralph
> Droms and Ted Lemon". This has a thorough (but very readable)
> explanation of how the protocol works and the different states the
> server & client can go through. It also explains why the protocol
> works the way it does, which is rather a case of "we wouldn't start
> from here" given a clean sheet. This is better than observing a
> specific client & server combination and inferring what's happening -
> it's not unknown (for example) for clients to misbehave.
>

I wasn't aware the subject issue before
Sorry for any inconvenience.

Also thanks for your help and suggestions!

-Derek

>
> --
> 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.
>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 9 May 2011 10:26:08 +0000 (UTC)
> From: Eduardo Henrique De Oliveira Gon?alves    <dupotter at gmail.com>
> Subject: Convite para conectar-se no LinkedIn
> To: <dhcp-users at isc.org>
> Message-ID:
>        <562582744.2534675.1304936768373.JavaMail.app at ela4-bed40.prod>
> Content-Type: text/plain; charset="utf-8"
>
> LinkedIn
> ------------
>
>
> Eu gostaria de adicion?-lo ? minha rede profissional no LinkedIn.
> -Eduardo Henrique
>
> Eduardo Henrique De Oliveira Gon?alves
> Analista de Suporte de TI na Grupo S?o Martinho
> Quirin?polis e redondezas, Brasil
>
> Confirme que voc? conhece Eduardo Henrique De Oliveira Gon?alves
> https://www.linkedin.com/e/-ah4dnp-gnh9nqlv-h/isd/2838541552/ILovxfWA/
>
>
>
> --
> (c) 2011, LinkedIn Corporation
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.isc.org/pipermail/dhcp-users/attachments/20110509/368da467/attachment-0001.html
> >
>
> ------------------------------
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
> End of dhcp-users Digest, Vol 31, Issue 17
> ******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20110509/393b0bfe/attachment.html>


More information about the dhcp-users mailing list