<html><body><div style="font-family: Andale Mono; font-size: 10pt; color: #000000"><div style="font-family: Andale Mono; font-size: 10pt; color: #000000">Question ... I noticed option 82 information in your packet dump. How is that ending up in there?</div><div style="font-family: Andale Mono; font-size: 10pt; color: #000000"><br data-mce-bogus="1"></div><div style="font-family: Andale Mono; font-size: 10pt; color: #000000">The packet dump doesn't appear to show a relay agent in play, so option 82 shouldn't exist...<br><br><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Sean McMurray" <sean@mvtel.com><br><b>To: </b>"Users of ISC DHCP" <dhcp-users@lists.isc.org><br><b>Sent: </b>Tuesday, June 9, 2015 1:30:13 PM<br><b>Subject: </b>Re: dhcpd doesn't acknowledge dhcp requests<br></blockquote></div><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;">I have stripped dhcpd.conf all the way down to this:<br><br> log-facility local6;<br><br> subnet 10.112.0.0 netmask 255.248.0.0 {<br> option routers 10.112.0.1;<br> pool {<br> range 10.112.1.0 10.112.255.255;<br> }<br> }<br><br>I have disabled SELinux. I have disabled iptables.<br>I have purged the leasefile.<br>Still, dhcpd does not respond to DHCPDISCOVERs.<br><br><br>On 06/08/2015 03:21 PM, Peter Rathlev wrote:<br>> On Fri, 2015-06-05 at 14:49 -0700, Sean McMurray wrote:<br>>> strace shows the daemon receiving requests but not responding.<br>>> I'm stumped as to why it won't respond.<br>> That certainly seems strange. Have you tried removing the log statements<br>> completely? I would call it a bug if that changes anything, but it would<br>> be easy to try.<br>><br>> With the stock CentOS 7 package it should not be SELinux related, unless<br>> there was an error in the definitions. However, could you try disabling<br>> SELinux if you haven't already?<br>><br>> Other than that I can only think of starting the daemon with a trace<br>> file (-tf flag), which should let someone with adequate skills figure<br>> out exactly what happens inside the process.<br>><br><br><br>_______________________________________________<br>dhcp-users mailing list<br>dhcp-users@lists.isc.org<br>https://lists.isc.org/mailman/listinfo/dhcp-users</blockquote></div></div><br></div></body></html>