My configuration is very simple. There are no hooks, no HA, no multi-threading,
no fancy commands.
Postgres version is 12.7
Gordon.
On 06/07/2021, 19:27, "Marcin Siodelski" wrote:
Gordon,
Thanks for posting your issue to the Kea users list. I will try to
replicate your issue tom
I was able to hack around this (limitation?) (using some snippets found in
earlier mailing list posts) with the following config.
Please note that this will not work if there is more than one relay being done
as it will probably be substring(relay6[some integer greater than
0].option[18].hex,0
Gordon,
Thanks for posting your issue to the Kea users list. I will try to
replicate your issue tomorrow with the Postgres lease database backend.
It will be super useful if you send me your Kea configuration file. You
can sanitize it from any private stuff it may contain. Please send it to
me pr
I am having the same issue with 1.8.2
I can delete the lease directly on SGBD but Kea can't.
Same error appears to me.
Regard,
Jerônimo
Em ter., 6 de jul. de 2021 às 13:28, Gordon Ross escreveu:
> On the off chance, I tried an upgrade to Kea 1.9.9 and the problem
> persists.
>
> Gordon.
>
>
On the off chance, I tried an upgrade to Kea 1.9.9 and the problem persists.
Gordon.
On 05/07/2021, 16:16, "Kea-users on behalf of Gordon Ross"
wrote:
I'm running Kea 1.8.2 using the Postgres lease database backend on Ubuntu
20.04 LTS
Devices can get a new IPv4 address fine. But whe
In Kea DHCPv6, I noticed that option 18 "interface-id" is not stored in the
lease6 table in mysql. There isn't a column for it. Is it possible to include
option 18 in the "logging" options if it isn't to be stored with the leases?
With debug on I can see it is received:
relay[0]: msg-type=12
In the DHCPv6 server, is it possible to reserve an IP address by
interface-id(18)? I tried what I thought might work:
{
"Dhcp6": {
"reservations": [
{
"interface-id": "Gi0/0/1.240",
"ip-addresses": [
"2001:0:2:8::abcd"
]
}
]
}
}
It produce
