Hi all,
I configured DHCP server on Mikrotik for my Ruckus APs.
I have two questions :
First : When I display the distributed addresses I see no MAC address Only zeros, why? :
Example :
Address 192.168.11.130
MAC Address 00:00:00:00:00:00
Client ID
Server dhcp2

Second: How can I configure Option 43 on Mikrotik to point APs to the Ruckus controller IP address?

Thank you

For DHCP option try:
https://wiki.mikrotik.com/wiki/Manual:I ... CP_Options

the link does not talk about option 43.
any idea why the DHCP leases display the source MAC with zeros ??
Regards

the link does not talk about option 43.

The link talks about how to add any user-provided option into DHCPOFFER and DHCPACK in general. It is your task to find the required contents and its format for this option in the Ruckus documentation and set the the IP address (or domain name?) in the necessary format in the /ip dhcp-server option add code=43 name=O43-for-ruckus value=???? command.

any idea why the DHCP leases display the source MAC with zeros ??

None, but if you set the destination file name under /tool sniffer and then run /tool sniffer quick interface=xxx ip-protocol=udp port=68 and let the client ask for address, you can use Wireshark to see the contents of the DHCPDISCOVER / DHCPREQUEST. If everything else works, I assume the client-mac-address field in there will be 00:00:00:00:00:00.

Thank you for your replay .
For DHCP option I did this : /ip dhcp-server option add code=43 name=Ruckus value='192.168.11.253' , is that correct?
for MAC with zeros , I'm not talking about one client, leases display all the client's MAC are with zeros ( for info the client are Ruckus WAP).
please note that in the same router I have a second dhcp pool for GUEST and it's working fine (the dhcp display the correct MAC address), the issue is only happen with the pool for Ruckus APs.is that related to ruckus APs or something wrong in the mikrotik configuration?

For DHCP option I did this : /ip dhcp-server option add code=43 name=Ruckus value='192.168.11.253' , is that correct?

I have neither the Ruckus documentation nor a crystal ball, so I can't say, but likely not as Option 43 is for vendor specific information so I'd expect its internal structure to be more complex.
But wait, there's Google search, and a search for "ruckus dhcp option 43" reveals this page.

for MAC with zeros , I'm not talking about one client, leases display all the client's MAC are with zeros ( for info the client are Ruckus WAP).
please note that in the same router I have a second dhcp pool for GUEST and it's working fine (the dhcp display the correct MAC address), the issue is only happen with the pool for Ruckus APs.is that related to ruckus APs or something wrong in the mikrotik configuration?

Please note that there is no setting which would make Mikrotik's /ip dhcp-server or /ip pool behave in a special way in this regard. But from what you wrote it comes out that all the clients which are reported as having MAC address 00:00:00:00:00:00 have two things in common:

• they use the same server and pool
• they are Ruckus WAPs

. So what about connecting one of the WAPs to the port served by the server/pool which doesn't show any problem and see whether the issue follows the WAP or not?

I tried different way, some no Ruckus devices taking and displaying their real MAC on the same Pool, and also few Ruckus WAP also displaying their MAC, but majority display zeros. So I think it's related to the device not the DHCP Server. I thought in the beginning that maybe it's something related to the ARP inspection or something else.

I use DHCP option 43 but for Ubiquiti UAPs. Your mistake is - IP address in option 43 should be in hex, for example 192.168.0.15 in hex is c0a8000f. Also for UAP you need to add 0104 in front of hex IP address, in my example the value for option 43 should be 0104c0a8000f

Has anyone figured out how to use the undocumented vendor-class-id CLI? It doesn't seem to have anything to match on the class identifier in the request so I have no idea how it's supposed to work.

IP address in option 43 should be in hex

It's not that simple. The contents is as per vendor specification, so one vendor may require just an ip address as 4 bytes while another one may require a text string to be interpreted as fqdn or IP number.

I understand, thanks sindy. My experience is only with UniFi APs.

For what I see, vendor-class-specific option-43 delivery is not implemented yet ... it's possible to have a specific ip-pool based on the vendor-class-id, but it's neither possible to add an dhcp-option-set to an ip-pool nor is there any matching condition-parm in the option-43-definition.
So what's not in the documentation ... may not be there ?!

just had a look in v7 beta4 ...
. .
here we go, with v7-4 you can glue an option-set to your vendor-class-id ...( CLI only ! )

to be honest ... hopefully this feature will find it's way into v.6.4.x too ... while v7 is simmering.
... guess we will see (maybe one or another afficionado will give me "a ball plus" here : )

For what I see, vendor-class-specific option-43 delivery is not implemented yet ... it's possible to have a specific ip-pool based on the vendor-class-id, but it's neither possible to add an dhcp-option-set to an ip-pool nor is there any matching condition-parm in the option-43-definition.

I would say put the APs on a separate management VLAN and configure a separate DHCP server for that VLAN with the desired option.
It would be a good idea to have a management VLAN anyway...

divide et impera ... I agree by 100%
... but when 2000 ip-phones fresh outta box staring at you, you will beg for your vendor-class-based dhcp-features ...
Sometimes you want split the ip-address-space for your VoIP by building ... add 4 types of phones (or AP's) and you will go nuts very soon

... so far as I recall ... it was a thorny way to implement in ISC too ( for me : ) ... but there's lot of time till january 6th
. .
we are on our way here