Nicolas.
>
> De : Kea-users [mailto:kea-users-boun...@lists.isc.org] De la part de itay
> cohen
> Envoyé : vendredi 11 mai 2018 02:35
> À : kea-users@lists.isc.org
> Objet : [Kea-users] option 54
>
> hi all
>
> i'm using kea-1.2.0
>
> i
cohen9...@gmail.com>, kea-users@lists.isc.org
Subject: Re: [Kea-users] option 54
Option 54 is set automatically by the server (to the IP address on which the
packet was received, I think).
It cannot be an arbitrary value, it is used by clients in DHCPREQUEST messages.
The server wil
@lists.isc.org
Objet : [Kea-users] option 54
hi all
i'm using kea-1.2.0
i'm trying to set
"option-data": [
{ "name": "routers", "data": " 10.0.0.1" },
{ &q
Ok, thanx.
Just wanted to be sure that i didn't misconfigured the server.
So far i have manage to bypass the problem by creating buffer_receive
and pkt_send hooks.
pkt_send is changing server-id when sent to client (based on some
conditions).
buffer_receive is changing it back to server
We know the address given is server-identifier should get more control,
there are some tickets about this (and as far as I know no time to
deal with them soon...).
Regards
Francis Dupont
Igor Smitran writes:
> Hi list,
>
> Did any of you tried to set custom server-identifier
Hi list,
Did any of you tried to set custom server-identifier in a subnet?
In case you wonder why would one do that:
Server is in a private network, behind firewall. There is a dhcp relay
that forwards all requests to dhcp server.
But, when server leases a public ip to a cpe device then cpe