Setup guide

add-default-route (yes | no; default: yes) - whether to add the default route to the gateway
specified by the DHCP server
use-peer-dns (yes | no; default: yes) - whether to accept the DNS settings advertized by DHCP
server (they will appear in /ip dns submenu)
Command Description
renew - renew current leases. If the renew operation was not successful, client tries to reinitialize
lease (i.e. it starts lease request procedure (rebind) as if it had not received an IP address yet)
Notes
If host-name property is not specified, client's system identity will be sent in the respective field of
DHCP request.
If client-id property is not specified, client's MAC address will be sent in the respective field of
DHCP request.
It use-peer-dns property is enabled, the DHCP client will uncoditionally rewrite the settings in /ip
dns submenu. In case two or more DNS servers were received, first two of them are set as primary
and secondary servers respectively. In case one DNS server was received, it is put as primary
server, and the secondary server is left intact.
Example
To enable DHCP client on ether1 interface:
[admin@Wandy] ip dhcp-client> set enabled=yes interface=ether1
[admin@Wandy] ip dhcp-client> print
enabled: yes
interface: ether1
host-name: ""
client-id: ""
add-default-route: yes
use-peer-dns: yes
[admin@Wandy] ip dhcp-client>
DHCP Client Lease
ip dhcp-client lease
Description
This submenu shows the actual IP address lease received by the client
Property Description
status (read-only: "" | searching... | requesting... | bound | renewing... | rebinding...) - the current
state of DHCP client:
• "" - DHCP client is not enabled
• searching... - the DHCP client is searching for DHCP server, but has not yet received an offer
• requesting... - the DHCP client has received an offer from a DHCP server, and requesting an IP
address now
• bound - the DHCP client has received an IP address (status bound should also appear on the