Thanks Martjin, if I understand correctly you run 2 or more kea-dhcp4 daemons 
bound to different interfaces on the VM/server and with different config files?

Are you doing same for the control-agent, listening on 2 or more ports?

Thanks,

- Matthew

From: Kea-users <[email protected]> On Behalf Of Martijn Remmen 
via Kea-users
Sent: Tuesday, July 30, 2024 12:46 PM
To: Kea user's list <[email protected]>
Cc: Martijn Remmen <[email protected]>
Subject: Re: [Kea-users] Overlapping Subnets

[EXTERNAL EMAIL]
Hi Matt,

We have the same use case (running dhcp services for multiple VRFs). We run a 
kea instance for each vrf. Back when we researched this, it was not possible 
with a single kea instance.

We have a systemd template for the kea service, and can manage the service with 
‘systemctl start kea-dhcp4@vrf111’.

It has its pros and cons. I guess you could also look at containers.

We previously used LXC, but had issues with maintaining all the containers. I 
feel like our current solution is a lot easier to maintain.

Let me know if you have any questions.

Regards,

Martijn


Op 30 jul 2024 om 18:16 heeft Matt Aiken via Kea-users 
<[email protected]<mailto:[email protected]>> het volgende 
geschreven:

Thank you, Darren and Peter.

My use case involves managing the address spaces for different VRFs in our 
network, which may have overlapping or duplicate addresses.

I can achieve the required functionality using option 82 information added by 
my relay to choose between VRFs. However, this method breaks down when I 
introduce a subnet that exists in both VRFs.

The only alternative I can think of is to run separate instances of Kea for 
each VRF. However, I was hoping to simplify things by using a single server and 
leveraging option 82 information.

Thanks,

- Matthew
This e-mail may contain information that is confidential or privileged. If you 
are not the intended recipient, do not read, copy or distribute the e-mail or 
any attachments. Instead, please notify the sender and delete the e-mail and 
any attachments. Thank you. --
ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.

To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.

Kea-users mailing list
[email protected]<mailto:[email protected]>
https://lists.isc.org/mailman/listinfo/kea-users
This e-mail may contain information that is confidential or privileged. If you 
are not the intended recipient, do not read, copy or distribute the e-mail or 
any attachments. Instead, please notify the sender and delete the e-mail and 
any attachments. Thank you.
This e-mail may contain information that is confidential or privileged. If you 
are not the intended recipient, do not read, copy or distribute the e-mail or 
any attachments. Instead, please notify the sender and delete the e-mail and 
any attachments. Thank you.
-- 
ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.

To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.

Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users

Reply via email to