Maybe I will just inject via ubus a prefix, that is not reflected by the
config, like the
"UBUS_METHOD("add_prefix", handle_add_prefix, prefix_attrs)"
At the end that gives me the flexibility I need without the need to
insert absolute timestamps.
Best,
Nick
On 2/6/21 9:33 PM, Nick wrote:
I s
I see that more as setting a preferred lifetime with a relative time-span.
E.g. I will get a a preferred_lft of 120 from now, and I would set it like:
date '+%d %b %Y %T' --date="@$(($(date +%s)+120))"
So it does not need to be synced, since I'm only interested in the
timespan from now + 120s
On Sat, Jan 30, 2021 at 5:33 PM Nick Hainke wrote:
>
> Until now it is not possible to give absolute timestamps in odhcpd.
> This means that on every new RA or request, the timestamp is renewed.
> Further, the valid and preferred lifetimes are not synced between all
> devices.
>
> There are severa
