On 08/10/18 11:39, Bernard CLABOTS wrote:
> => So My iPhone is legit.
>
> "Servers with knowledge of the client's configuration parameters
>
> respond with a DHCPACK message to the client. Servers SHOULD NOT
> check that the client's network address is already in use; the
>
Hi Simon, I am definitely not a DHCP expert and I don't want either to
become a pain. Yet... I can read that not only the behavior is not inline
with RFC, but it even contradicts the RFC:
"3.2 Client-server interaction - reusing a previously allocated network address
If a client
Hi Simon, Sorry to come back to this question again. You wrote:"I don't think
it would be possible to make this hack any more safe by
doing the ping-check before re-creating the lease. The whole premise is
that the client attempting to renew is already configured, but the
server lost track of
On 19/09/18 11:09, Bernard CLABOTS wrote:
> Thanks a lot for this answer.
>
> Indeed, it is a special case as we have a simple two way Request/ACK,
> this is also what is seen with some implementations when quickly
> unplugging/re-plugging the cable, it is legal AFAIK.
>
> I also agree on the
Thanks a lot for this answer.
Indeed, it is a special case as we have a simple two way Request/ACK, this is
also what is seen with some implementations when quickly unplugging/re-plugging
the cable, it is legal AFAIK.
I also agree on the necessity to be efficient in case of loss of the lease dB.
On 18/09/18 16:59, Bernard CLABOTS wrote:
> Hi all,
> I have been trying to replicate an issue of IP conflict on Open-WRT,
> the issue is randomly seen, and I expect in real life, it is related to
> a de-sync of the lease data base with the actual situation (in case a
> switch is between the
Hi all, I have been trying to replicate an issue of IP conflict on Open-WRT,
the issue is randomly seen, and I expect in real life, it is related to a
de-sync of the lease data base with the actual situation (in case a switch is
between the client and the server and the server is rebooted
