<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 5/11/2020 8:25 PM, Joshua Schaeffer
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:b0b7f373-c867-aff3-1813-e1bff26f722b@harmonywave.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
On 5/11/20 4:10 PM, Brian Hechinger wrote:<br>
<blockquote type="cite"
cite="mid:979ae544-7d28-91b6-5276-17e3b42fadfe@4amlunch.net">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<p>It never gets to the switch in the first place. Watching
tcpdump on the dhcp server I only see the requests coming in
but never sending anything out.</p>
</blockquote>
That's what I figured but wanted to be sure.<br>
<blockquote type="cite"
cite="mid:979ae544-7d28-91b6-5276-17e3b42fadfe@4amlunch.net"><br>
<p>Traceroute doesn't work oddly enough. It just times out.</p>
</blockquote>
That can be typical in some networks as a lot of firewalls drop
ICMP packets by default.<br>
</blockquote>
<p><br>
</p>
<p>There is no firewall in place though. packet path for this
traceroute should be: vm -> switch -> other interface on
same switch.</p>
<p><br>
</p>
<p>Something doesn't seem quite right here.</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:b0b7f373-c867-aff3-1813-e1bff26f722b@harmonywave.com">
<blockquote type="cite"
cite="mid:979ae544-7d28-91b6-5276-17e3b42fadfe@4amlunch.net">
<blockquote type="cite"
cite="mid:98d40bff-5a53-c740-4c44-d871fb3e9fde@harmonywave.com"><font
face="Droid Sans Mono"> </font>- How is Kea's
interfaces-config map configured in kea-dhcp4.conf<font
face="Droid Sans Mono">?</font></blockquote>
<br>
<font face="Droid Sans Mono"> "interfaces-config": {<br>
"interfaces": [ "*" ],<br>
"dhcp-socket-type": "udp"<br>
},</font><br>
</blockquote>
AFAIK everything looks fine. Can't give you an definitive answer
as to why when Kea sends a packet the OS thinks the host has no
route:<br>
<br>
- Could be a firewall or security context issue. Check IPTables,
AppArmor, SELinux, etc.<br>
</blockquote>
<p><br>
</p>
<p>None of those are running, no.</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:b0b7f373-c867-aff3-1813-e1bff26f722b@harmonywave.com"> -
As a test you could try changing to raw sockets (remove <font
face="Droid Sans Mono">"dhcp-socket-type": "udp"</font>). If
that does work I'm not sure why it would as it's a relayed
request.<br>
</blockquote>
<p><br>
</p>
<p>Didn't make a different.</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:b0b7f373-c867-aff3-1813-e1bff26f722b@harmonywave.com"> -
Force Kea to use the kernel routing table by adding <font
face="Droid Sans Mono"><span class="s2">"outbound-interface"</span><span
class="p">:</span> </font><span class="s2"><font face="Droid
Sans Mono">"use-routing" </font>to the configuration (after
re-adding <font face="Droid Sans Mono">"dhcp-socket-type":
"udp"</font> back to the config).</span></blockquote>
<p><br>
</p>
<p>Now it silently fails. Kea *thinks* it sent the packet but it
never goes anywhere.</p>
<p><br>
</p>
<p>I'm going to dig into this weird networking that's going on here
because I'm starting to think it's definitely not Kea who is to
blame here.</p>
<p><br>
</p>
<p>-brian<br>
</p>
</body>
</html>