DHCP options to static assigned clients

RouterOS General
1

I set up simple DHCP server on test Mikrotik with stable version (6.32.4):

/ip dhcp-server
  add add-arp=yes address-pool=pool-LAN authoritative=yes disabled=no interface=ether1 lease-time=1d name=LAN src-address=192.168.1.1

/ip dhcp-server network
  add address=192.168.1.0/24 dhcp-option=sip_init dns-server=192.168.1.1 gateway=192.168.1.1 netmask=24 ntp-server=194.190.168.1

/ip dhcp-server option
  add code=66 name=sip_init value="'http://192.168.1.10/panasonic/'"

When I set that up all “dynamic” clients receives that option (which is quite good), while when I set any client as “static”, and then add that option to client’s config:

/ip dhcp-server lease
  add address=192.168.1.20 comment="phone1" dhcp-option=sip_init mac-address=xx:xx:xx:xx:xx:xx server=LAN

the client won’t get any DHCP option(s).

I also tried to create option set and assign it to client:

/ip dhcp-server option sets
  add name=phones options=sip_init

/ip dhcp-server lease
  add address=192.168.1.20 comment="phone1" dhcp-option=sip_init dhcp-option-set=phones mac-address=xx:xx:xx:xx:xx:xx server=LAN

still no luck.

Any ideas how to fix that, so ‘static’ assigned client to receive DHCP option(s)? I deploy some ip phones and prefer to reconfigure it with DHCP option 66, and not via visiting each phone web interface (that’s quite slow way).

2

Why would you assign it to a static entry? Set the options on a per network basis, leaving the option field blank on the static lease itself.

What happens if you just assign an option set (not option set and option) on the static lease?

3

To be able to find my devices exactly on places it intended to be. In fact, I assign IPs to users dynamically from 192.168.1.100…199, while assign IP to devices statically from 192.168.1.20..99. Easy to maintain, and printers, ip phones etc are always at their places.

Will test, haven’t tried yet.

As I’ve stated, 6.32.4 (“stable” branch). Prefer to stay stable, non needed new features in such a small network.

4

Of course… what I meant, is why do you set the sip_option on a per static entry basis when you have set it on a per network basis already?

I guess all phones would have a common PBX, so its tidier and more efficient to have just the network entry, that having to maintain each static lease entry.

5

Of course… what I meant, is why do you set the sip_option on a per static entry basis instead of setting it on a per network basis?

I guess all phones would have a common PBX, so its tidier and more efficient to have just the network entry, that having to maintain each static lease entry.[/quote]

Got your point but I failed to recieve DHCP option in any way, only by setting in in network (the way I did that initially), by setting it in static entry.

Will try to intercept packets but due to network configuration this is a bit hard to do.

6

You can enable DHCP debug at the router and have a look there.

Do you have another mikrotik device at hand? I’d use it to set a dhcp-client to debug from a client perspective.

Is this a small installation? Good practice for VoIP is having its own network segment (layer 2), and of course its own network range, say 192.168.2.0.

I always setup phones this way, and then set dhcp options on the network dhcp entry.

Sorry about the ROS version, I got mixed up :smiley: Is firmware up to date?