Hi,
We do a lot of Docsis provisioning with our Mikrotik Routers.
These are large networks of 200+ modems and every modem has a static DHCP so we can monitor each individual device.

The provisioning is done via the docsis bootfile that tells the modems what its settings are.
The bootfile has to be specified via bootp and cannot be send as DHCP option.
So under networks we specify the bootfile name and each DHCP lease gets send this bootfile name to do its TFTP request.

However since our networks start growing, we see that we have to use different types of modems in networks and this poses a problem.
Every type of modem needs its specific bootfile. And even in a certain type of modem we have modems performing different roles, for example some function as router and others as hotspot bridge.

For now we solve this problem bij adding several ip subnets to our network so each type of modem gets it own subnet,
And for different roles we use the TFTP server and specify the bootfile per IP address.

It would however be so much more flexible if we could specify the bootfilename per individual DHCP lease or under the DHCP option tab.
Or the option to specify a bootfile depending on the informartion provided by the modem in its DHCP request.

BR.
Ammer

It sounds like you are using the Mikrotik as a DHCP Server and possible the TFTP Server? If so, could you not do a DHCP Relay setup to a Linux (or something else) based DHCP Server that handles the requests? This would give you a more feature rich implementation.

--Greg

Hi Greg,

Yes we are using the Mikrotik as DHCP and TFTP server.
We are running it on a x86 platform with plenty of processing power and storage space.
We like to keep our setup fairly compact.
From a management and financial point o view its also more efficient to run all the processes on a single system.
Thats why we aren't running a separate DHCP and TFTP server.

BR.
Ammer

Yes we are using the Mikrotik as DHCP and TFTP server.
We are running it on a x86 platform with plenty of processing power and storage space.
We like to keep our setup fairly compact.
From a management and financial point o view its also more efficient to run all the processes on a single system.
Thats why we aren't running a separate DHCP and TFTP server.

I understand where you are coming from. I just don't think MikroTik has any plans on making a super feature rich DHCP Server.

Since you are running on x86, have you thought about creating an Linux KVM Guest for your DHCP Server? You would be able to run everything on the one box, but still get the best of both worlds.

--Greg

HI Greg,

Running the Mikrotik and Linux DHCP as VM has crossed my mind.
However we have never done this and don't want to compromise the stability of our current systems. These are production environments.

As i stated in my first post, we can always find a workaround but the ability to do it all from within the Mikrotik would be a great feature for us.
Like you said, it doesn't seem Mikrotik is planning on enhancing the features of the DHCP server, but i though let me just throw it in here, hoping someone from Mikrotik might think its a good idea

The option to add bootfile names on separate DHCP leases is a feature that isn't too complicated to implement in my humble opinion.
It basically exists, just one level too low

Ammer

I agree. I've always wanted a Mac Address Range field within the DHCP Server Networks. That would allow everyone to specify different options for all the devices out there.

--Greg

Hi Ammer,

can you help me to do Docsis provisioning with Mikrotik ?
Or maybe post an export of your router?

Thanks.