[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dhcp-users
Subject:    Re: dhcp-users Digest, Vol 31, Issue 16
From:       Derek Wang <xiangshu129 () gmail ! com>
Date:       2011-05-09 5:14:05
Message-ID: BANLkTikXCi67eJpvNGbO7cv6ExGDC33Qrg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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

[Attachment #5 (text/html)]

Simon, you mentioned in last paragraph that we also need to make sure the client can \
contact the server via unicast after<br>got the IP in the client side, it&#39;s right \
because the client need to send the DHCPREQUEST packet to the dhcp server to \
renew<br> the information.<br><br>But If the client can not contact dhcp server via \
unicast, like without correct route info, then what will happen?<br>I think the \
client will time out after the max-lease-time, then the client will initiate the \
DHCPDISCOVER again,<br> 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<br>the server side \
see the DHCPDISCOVER packet, but the server will not return the DHCPOFFER to the \
relay, then to<br> the client. And when I return to check the client&#39;s expire \
info, and the result is 1969 Wed Dec 31 23:59:59 1969, but the<br>output is 2011 Mon \
May 09 04:53:23 2011 after the client get the dhcp info successfully first time. \
It&#39;s so weird. Is that<br> expected?<br clear="all"><br>thanks!<br>-- <br>Best \
Regards,<br>Derek Wang<br>



_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users

[prev in list] [next in list] [prev in thread] [next in thread]