<div dir="ltr">Turning off the udp dhcp-socket-type and disabling the DHCP relay did work in that my systems were getting IP addresses assigned to them.<div><br></div><div>However, even though I have reservations for just about everything in my network, the systems were getting IP addresses out of scope from their reservations.</div><div><br></div><div>A system on vlan11 with an IP address of 192.168.11.XXX was getting assigned an address of 192.168.10.XXX.</div><div><br></div><div>I'll have to dig into the logs to see why this might be, but it could also be because I don't have the firewall rules tightened between the vlans and traffic from one vlan can get to another.</div><div><br></div><div>Once I set things back to the udp dhcp-socket-type and turned the DHCP relay back on, the systems got the appropriate address.</div><div><br></div><div>I just assumed that since I had interfaces on each of the vlans that each system on its respective vlan would get its appropriate address.</div><div><br></div><div>Unless I might have something else misconfigured?</div><div><br></div><div>-Ubence</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 2, 2024 at 1:18 PM Ubence Quevedo (thatrat) <<a href="mailto:thatrat@gmail.com">thatrat@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Yes, here’s the interface-config section that I have defined:<div><div><font face="Courier New"> "interfaces-config": {</font></div><div><font face="Courier New"> "interfaces": [ "eno2/<a href="http://192.168.10.3" target="_blank">192.168.10.3</a>","eno2.11/<a href="http://192.168.11.3" target="_blank">192.168.11.3</a>","eno2.12/<a href="http://192.168.12.3" target="_blank">192.168.12.3</a>" ],</font></div><div><font face="Courier New"> "dhcp-socket-type": "udp",</font></div><div><font face="Courier New"> "service-sockets-max-retries": 5,</font></div><div><font face="Courier New"> "service-sockets-retry-wait-time": 5000</font></div><div><font face="Courier New"> },</font></div><div><br></div><div>…and from further reading on the interfaces-config section, specifically the dhcp-socket-type configuration:</div><div>Using UDP sockets automatically disables the reception of broadcast packets from directly connected clients. This effectively means that UDP sockets can be used for relayed traffic only. When using raw sockets, both the traffic from the directly connected clients and the relayed traffic are handled.</div><div><br></div><div>So…I’m doing this to myself. 😖</div><div><br></div><div>I’m assuming I should either remove this line or set it to raw, which are effectively the same thing I believe [I like to have fully qualified configs when possible to take out the guess work].</div><div><br></div><div>Once I do this though and restart the service, I think I can disable the relay and then the interfaces should start picking up the traffic.</div><div><br></div><div>-Ubence</div><div><br><blockquote type="cite"><div>On Aug 2, 2024, at 8:34 AM, Sonic <<a href="mailto:sonicsmith@gmail.com" target="_blank">sonicsmith@gmail.com</a>> wrote:</div><br><div><div dir="ltr">Are you by chance using:<div> "dhcp-socket-type": "udp"</div><div>for the interfaces in question?</div><div><br></div></div>
-- <br>ISC funds the development of this software with paid support subscriptions. Contact us at <a href="https://www.isc.org/contact/" target="_blank">https://www.isc.org/contact/</a> for more information.<br><br>To unsubscribe visit <a href="https://lists.isc.org/mailman/listinfo/kea-users" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a>.<br><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" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a><br></div></blockquote></div><br></div></div></blockquote></div>