<div dir="ltr"><br><div>Hi Maxime,</div><div><br></div><div>Have you defined the subnet as one that's owned by Kea in the config file? Assuming you have different routers, netmasks, etc., you would have to define a separate scope for both networks.</div><div><br></div><div>Presumably you've got DHCP forwarding enabled on your switches as well so that DHCP requests get relayed through to your Kea server, which is the only way you can have any DHCP server provide leases for a network it is not directly connected to.</div><div><br></div><div>If it's useful, here's a sample from my config that serves three different subnets via a single NIC on a different network:</div><div><br></div><div>-- cut --<br> "subnet4": [<br> {<br> "subnet": "<a href="http://10.129.129.0/29">10.129.129.0/29</a>",<br> "id": 1,<br> "pools": [{ "pool": "10.129.129.2 - 10.129.129.6" }],<br> "option-data": [{ "name": "routers", "data": "10.129.129.1" }]<br> },<br> {<br> "subnet": "<a href="http://10.129.129.8/29">10.129.129.8/29</a>",<br> "id": 2,<br> "pools": [{ "pool": "10.129.129.10 - 10.129.129.14" }],<br> "option-data": [{ "name": "routers", "data": "10.129.129.9" }]<br> },<br> {<br> "subnet": "<a href="http://10.0.194.0/28">10.0.194.0/28</a>",<br> "id": 3,<br> "pools": [{ "pool": "10.0.194.2 - 10.0.194.14" }],<br> "option-data": [{ "name": "routers", "data": "10.0.194.1" }]<br> }<br> ]<br>-- cut --</div><div><br></div><div>cheers,</div><div>Klaus</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 15, 2016 at 5:08 AM, Maxime Lareo <span dir="ltr"><<a href="mailto:max.lareo@gmail.com" target="_blank">max.lareo@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I currently testing KEA with 2 servers for HA with a Mariadb Galera Cluster Backend and it works pretty well.<br>
<br>
It running like a charm with one subnet, but when it come managing multiple subnet, with only 1 NIC, it seems impossible to make it work. KEA just doesn't want to give an IP address that doesn't belong to its own subnet.<br>
<br>
I don't succeed to use ip relay or client classification properly to make it work.<br>
<br>
Do I missing something ?<br>
<br>
I just want to have VoIP devices on another subnet than the original subnet. All the devices (VoIP or not) are on the same VLAN and switch.<br>
<br>
To explain my actual configuration :<br>
<br>
I have a client classes testing the option 60 and it work, I can see in the log file, the expression evaluated to 1, but KEA doesn't choose the subnet with the client-class but the one who match its subnet (the one my server ip address belong to), which is after the VoIP subnet in the conf file.<br>
<br>
Someone know a way to make it works ?<br>
<br>
Thank you !<br>
______________________________<wbr>_________________<br>
Kea-users mailing list<br>
<a href="mailto:Kea-users@lists.isc.org" target="_blank">Kea-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/<wbr>listinfo/kea-users</a><br>
</blockquote></div><br></div>