DHCP relay/server vlan sub-interfaces

[#1]

OS 2.8 MR9 FW-60 and FG-500 Context : * vlan subinterface added to internal primary interface * vlan subinterface has ip address / mask (10.10.10.254/24) * internal primary interface not used * dhcp server setup on vlan subinterface * dhcp server configured to deliver leases with ip range (10.10.10.1 -> 10.10.10.12) Issue : * Fortigate unit does not answer lease queries (packet sniffing shows broadcast queries but no answer from fortigate) This problem is present on both FG-500 and FW-60 Help needed. Thank you Regards Samir Sow

[UkWizard]

So have you configured the DHCP relay properly on the external interface ?

[Darune]

Whats the name of the interface?

[#4]

The primary interface is internal The name of the vlan sub-interface is internal-vl-020 The dhcp was correctly configured Samir Sow

[UkWizard]

So you have setup an DHCP relay entry on the external interface, to the dhcp servers ip address (which is on the vlan subnet) and the dhcp server has the fortinets address as its default gateway ? yes ?

[#6]

I have configured a dhcpd server not a relay. The dhcp is configured on the sub-interface internal-vl-020

[UkWizard]

Oh i see, when i saw relay in the subject, i presumed you had a server in the vlan. I take it You are trying to use the fortinet as the dhcp source. If that doesnt work i wouldnt be surprised. DHCP over vlan, being supplied by a firewall .... sounds dodgy to me.

[Darune]

This will sound really strange, but try giving the vlan a shorter name, less than 14 characters. int-vl-20 or something like that, I' m almost positive that will fix it.

[#9]

Why would the name length be the cause of this problem ?

[skyhigh]

Darune has the right idea. We later included more measures to prevent administrators from using interface names longer than 14 characters but this is post-MR10. ECO #280-3304 DHCP-SERVER-CLI: Do not accept interfaces with name longer than 14 characters