How to let the DHCP client eventually accept a OFFER when no OFFER satisfies client's requirement?

[Chengyu Fan]

Hi~ Vasiliy,

I try to do the two-step discover as you suggested.
But when the first dhclient fails to find such OFFER, I don't know how to
stop the first one and launch the second dhclient. At this moment, the
first dhclient will run as a deamon and request IP latter. So if I launch
the second dhclient, I think they will conflict with each other, aren't
they?

How do you think?

Thanks,

On Thu, Jun 14, 2012 at 3:37 PM, Chengyu Fan <chengy.fan at gmail.com> wrote:

> Yes, this is one way to do it. But ideally I want this can be done by one
> dhclient.
>
> If its impossible to do it by one dhclient, how to do it in your way? Do I
> need to modify the code? Or just do the configuration is OK?
>
> Thanks,
>
> On Thu, Jun 14, 2012 at 3:33 PM, Vasiliy Molostov <molostoff at gmail.com>wrote:
>
>> **
>>
>> Is this the same as two step discover: one dhclient with conf A will
>> discover requesting ndn, and if it fails then fakllback to dhclient with
>> conf B where it is not require ndn?
>>
>>
>>
>> On Чт, 14 июн 12 14:57:20 Chengyu Fan wrote:
>>
>> What I want to do is when the DHCP client cannot get an OFFER in a time
>> period, he will learn that there is no such server, so he
>> will eventually choose one OFFER and request an IP.
>>
>>
>> Does anyone know how to do this by configuring the dhclient.conf?
>>
>>
>> Thanks,
>>
>>
>> Regards,
>> Chengyu Fan
>>
>>
>>
>>
>> _______________________________________________
>> dhcp-users mailing list
>> dhcp-users at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>
>
>
>
> --
> Regards,
> Chengyu Fan
>



-- 
Regards,
Chengyu Fan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20120614/6e3fb908/attachment.html>