vlan + dhcp server

Is it possible that the DHCP server doesn’t work on vlans (mikrotik 6.11)?
Still a bug?

I have 24 vlans with 24 dhcp servers, as yet works fine.
CCR-1016, ROS 6.11.

Maybe you’re trying to create vlans on ports directly without using a switch?

After upgrade from ROS 5.26 to 6.11 on RB1100AHx2, DHCP on vlan interfaces has stopped functioning properly.
The log says, the offer is sent to host with no success. The leases tab on DHCP show hosts with offered status (not bound).

I have tried to create bridge, adding vlan interface to bridge, and bound DHCP server to bridge with no success.

So I think it is definitely a bug.

Ok, we are resolving issue, [Ticket#2014042366000345].

What we already know:

In my case, the reson for which after upgrade to ROS 6.11/12 from 5.26 the DHCP server bounded to VLAN interface has stopped working is SWITCH !!
Yes, it is D-LINK DGS-1210-52 with DHCP Screening Feature (which allows only specified DHCP servers on specified ports to send offers). After entering here IP address of Mikrotik DHCP server, everything is working fine.

But, the question is, why DHCP on ROS 5.26 was working without IP address entered on switch.
This could be actually ROS 5.x bug, not 6.x :slight_smile:)
We will compare the offer packets structure from both ROS versions, and maybe find the answer.

yup, we have D-Link DES-3028 switches with DHCP Relay enabled, and v6 DHCP server leases IP addresses without default gateway (and, IIRC, with incorrect subnet mask). after disabling DHCP relay client gets correct settings

because of that we’ve moved to using virtual machine with v5.26 for DHCP :slight_smile:

lelo, any news?

Chupaka, I have given reply above. In my case the real reason was not Mikrotik but D-Link switch, that has no setting of allowed DHCP servers (DHCP screening feature)
The strange thing is, that it was working on ROS 5.x. without proper config on switch, but it was not normal condition.
Something must have changed in DHCP respones from 5.x to 6.x, but to investigate that it would be neccessary to perform packet capture and compare both responses.

well, I just thought you were going to compare packets from v5 and v6 :frowning:

we don’t use screening, just plain DHCP Relay on switches. also, those switches work with many linux and bsd servers, so I think it’s v6 who have broken DHCP server, not v5