dhcpd doesn't acknowledge dhcp requests

[dave c]

I don't recall seeing a line like this in your posted configurations:

interfaces "em2.112"

Dhcpd needs to be able to tell the difference between default vlan and an 802.1q tagged vlan 
that is residing on a virtual interface. The only way to do that is to tell it to listen to the 
alternative interface.

I believe it will also wish to know the definition of the default vlan and have it described as 
a network in the configs. It's been years since I've setup vlan tagged dhcp, but do recall I 
needed to enable the vlans in the configs before it would answer on them.

This page: http://serverfault.com/questions/412544/dhcp-server-for-multilple-vlans discusses 
someone else who had a similar issue with tagged vlans not getting answered.

Hope this helps...

Dave

On 6/11/15 12:58, Sean McMurray wrote:
> Yes. That is tagged vlan 112 on interface em2.
> dhtest fails if I include a -v 112 to tell it about vlan 112.
> What are the problems with tagged vlans?
>
> On 06/11/2015 04:00 AM, Graham Clinch wrote:
>> Hi,
>>
>>> #tcpdump -vv -i em2.112
>>                   ^^^^^^^
>> Is that tagged vlan 112 on interface em2? - I'd not spotted that previously.  I've never tried
>> it personally, but my recollection of posts to this list is 'dhcpd and tagged vlans don't mix
>> well'.
>>
>> Does dhtest fail if run from a different device?  If so, I guess it's really going over the
>> (presumably untagged) loopback interface.
>>
>> Are you able to present vlan 112 untagged?
>>
>> Graham
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users

-- 
Dave Calafrancesco