Manual:IPv6/DHCP Client: Difference between revisions

From MikroTik Wiki
Jump to navigation Jump to search
← Older edit
 
(23 intermediate revisions by 3 users not shown)
Line 3: Line 3:
==Summary==
==Summary==


Currently DHCPv6 client can receive only delegated prefix from DHCPv6-PD server.
DHCP-client in RouterOS is capable of being a DHCPv6-client and DHCP-PD client. So it is able to get a prefix from DHCP-PD server as well as DHCPv6 stateful address from DHCPv6 server.


==Quick setup example==
==Quick setup example==
Line 10: Line 10:


<pre>
<pre>
/ipv6 dhcp-client add pool-name=test-ipv6 pool-prefix-length=64 interface=ether13
/ipv6 dhcp-client add request=prefix pool-name=test-ipv6 pool-prefix-length=64 interface=ether13  
</pre>
</pre>


Line 19: Line 19:
Flags: D - dynamic, X - disabled, I - invalid  
Flags: D - dynamic, X - disabled, I - invalid  
  0    interface=bypass pool-name="test-ipv6" pool-prefix-length=64 status=bound  
  0    interface=bypass pool-name="test-ipv6" pool-prefix-length=64 status=bound  
       prefix=2001:db8:7501:ff04::/62  expires-after=2d23h11m53s  
       prefix=2001:db8:7501:ff04::/62  expires-after=2d23h11m53s request=prefix


</pre>
</pre>
Line 28: Line 28:
[admin@MikroTik] /ipv6 pool> print  
[admin@MikroTik] /ipv6 pool> print  
Flags: D - dynamic  
Flags: D - dynamic  
  #  NAME                        PREFIX                                     PREFIX-LENGTH
  #  NAME                        PREFIX                     REQUEST          PREFIX-LENGTH
  0 D test-ipv6                    2001:db8:7501:ff04::/62                               64
  0 D test-ipv6                    2001:db8:7501:ff04::/62     prefix                    64
</pre>  
</pre>  


Line 42: Line 42:
|prop=Property
|prop=Property
|desc=Description
|desc=Description
}}
{{Mr-arg-table
|arg=add-default-route
|type=yes {{!}} no
|default=no
|desc=Whether to add default IPv6 route after client connects.
}}
}}


Line 72: Line 79:
}}
}}


{{Mr-arg-table-end
{{Mr-arg-table
|arg=pool-prefix-length
|arg=pool-prefix-length
|type=string
|type=string
Line 79: Line 86:
}}
}}


{{Mr-arg-table
|arg=prefix-hint
|type=string
|default=
|desc=Include a preferred prefix length.
}}


{{Mr-arg-table
|arg=request
|type=prefix, address
|default=
|desc=to choose if the DHCPv6 request will ask for the address or the IPv6 prefix, or both.
}}
{{Mr-arg-table
|arg=script
|type=string
|default=
|desc=Run this script on the dhcp-client status change. Available variables:
* <var>pd-valid</var> - if the prefix is acquired by the client;
* <var>pd-prefix</var> - the prefix acquired by the client if any;
* <var>na-valid</var> - if the address is acquired by the client;
* <var>na-address</var> - the address acquired by the client if any.
* <var>options</var> - array of received options (only ROSv7)
}}
{{Mr-arg-table-end
|arg=use-peer-dns
|type=yes {{!}} no
|default=yes
|desc=Whether to accept the DNS settings advertised by the IPv6 DHCP Server.
}}
==Script==
It is possible to add a script that will be executed when a prefix or an address is acquired and applied or expires and is removed using DHCP client. There are separated sets of variables that will have the value set by the client depending on prefix or address status change as the client can acquire both and each of them can have a different effect on the router configuration.
Available variables for dhcp-client
* <var>pd-valid</var> - value - 1 or 0 - if prefix is acquired and it is applied or not
* <var>pd-prefix</var> - value ipv6/num (ipv6 prefix with mask) - the prefix inself
* <var>na-valid</var> - value - 1 or 0 - if address is acquired and it is applied or not
* <var>na-address</var> - value - ipv6 address - the address


==Status==
==Status==
Line 88: Line 136:
|prop=Property
|prop=Property
|desc=Description
|desc=Description
}}
{{Mr-arg-ro-table
|arg=duid
|type=string
|desc=Auto generated DUID that is sent to the server. DUID is generated using one of the MAC addresses available on the router.
}}
{{Mr-arg-ro-table
|arg=request
|type=list
|desc=specifies what was requested - prefix, address or both.
}}
}}


Line 128: Line 188:
}}
}}


To determine what IAID will be used, convert internal ID of an interface on which DHCP client is running from hex to decimal.
For example, DHCP client is running on interface pppoe-out1.
To get internal ID use following command
<pre>
[admin@t36] /interface> :put [find name="pppoe-out1"]
*15
</pre>
Now convert hex value 15 to decimal and you get IAID=21


==Menu specific commands==
==Menu specific commands==
Line 163: Line 234:
* Client routers uses received prefix to set up RA on the local interface
* Client routers uses received prefix to set up RA on the local interface


'''Configuration'''
'''R1'''
<pre>
/ipv6 route
add gateway=fe80::1:1%to-ISP
/ipv6 pool
add name=myPool prefix=2001:db8::/62 prefix-length=64
/ipv6 dhcp-server
add address-pool=myPool disabled=no interface=to-CE-routers lease-time=3m name=server1
</pre>
'''CE1'''
<pre>
/ipv6 dhcp-client
add interface=to-R1 request=prefix pool-name=my-ipv6
/ipv6 address
add address=::1/64 from-pool=my-ipv6 interface=to-clients advertise=yes
</pre>
'''CE2'''
<pre>
/ipv6 dhcp-client
add interface=to-R1 request=prefix pool-name=my-ipv6
/ipv6 address
add address=::1/64 from-pool=my-ipv6 interface=to-clients advertise=yes
</pre>
'''Check the status'''
After configuration is complete we can verify that each CE router received its own prefix
On server:
<pre>
[admin@R1] /ipv6 dhcp-server binding> print
Flags: X - disabled, D - dynamic
#  ADDRESS                                    DUID              IAID SERVER        STATUS
1 D 2001:db8:1::/64                            0019d1393536        566 server1        bound
2 D 2001:db8:2::/64                            0019d1393535        565 server1        bound
</pre>
On client:
<pre>
[admin@CE1] /ipv6 dhcp-client> print
Flags: D - dynamic, X - disabled, I - invalid
#    INTERFACE          STATUS        REQUEST      PREFIX                                   
0    to-R1              bound        prefix        2001:db8:1::/64 
[admin@CE1] /ipv6 dhcp-client> /ipv6 pool print
Flags: D - dynamic
#  NAME                PREFIX                              PREFIX-LENGTH
0 D my-ipv6              2001:db8:1::/64                                64
</pre>
We can also see that IPv6 address was automatically added from the prefix pool:
<pre>
[admin@CE1] /ipv6 address> print
Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local
#    ADDRESS                                    FROM-POOL INTERFACE    ADVERTISE
0  G 2001:db8:1::1/64                                      to-clients        yes     
..
</pre>
And pool usage shows that 'Address' is allocating the pool
<pre>
[admin@CE1] /ipv6 pool used> print
POOL        PREFIX                                      OWNER        INFO       
my-ipv6      2001:db8:1::/64                            Address      to-clients 
</pre>


{{cont}}
{{cont}}

Latest revision as of 08:27, 20 April 2020

Applies to RouterOS: v5.9 +

Summary

DHCP-client in RouterOS is capable of being a DHCPv6-client and DHCP-PD client. So it is able to get a prefix from DHCP-PD server as well as DHCPv6 stateful address from DHCPv6 server.

Quick setup example

This simple example demonstrates how to enable dhcp client to receive IPv6 prefix and add it to the pool. 

/ipv6 dhcp-client add request=prefix pool-name=test-ipv6 pool-prefix-length=64 interface=ether13


Detailed print should show status of the client and we can verify if prefix is received 

[admin@x86-test] /ipv6 dhcp-client> print detail 
Flags: D - dynamic, X - disabled, I - invalid 
 0    interface=bypass pool-name="test-ipv6" pool-prefix-length=64 status=bound 
      prefix=2001:db8:7501:ff04::/62  expires-after=2d23h11m53s request=prefix

Notice that server gave us prefix 2a02:610:7501:ff04::/62 . And it should be also added to ipv6 pools 

[admin@MikroTik] /ipv6 pool> print 
Flags: D - dynamic 
 #   NAME                         PREFIX                     REQUEST          PREFIX-LENGTH
 0 D test-ipv6                    2001:db8:7501:ff04::/62     prefix                     64

It works! Now you can use this pool, for example, for pppoe clients.

Properties

Sub-menu: /ipv6 dhcp-client


Property Description
add-default-route (yes | no; Default: no) Whether to add default IPv6 route after client connects.
comment (string; Default: ) Short description of the client
disabled (yes | no; Default: no)
interface (string; Default: ) Interface on which DHCPv6 client will be running.
pool-name (string; Default: ) Name of the IPv6 pool in which received IPv6 prefix will be added
pool-prefix-length (string; Default: ) Prefix length parameter that will be set for IPv6 pool in which received IPv6 prefix is added. Prefix length must be greater than the length of received prefix, otherwise prefix-length will be set to received prefix length + 8 bits.
prefix-hint (string; Default: ) Include a preferred prefix length.
request (prefix, address; Default: ) to choose if the DHCPv6 request will ask for the address or the IPv6 prefix, or both.
script (string; Default: ) Run this script on the dhcp-client status change. Available variables:
  • pd-valid - if the prefix is acquired by the client;
  • pd-prefix - the prefix acquired by the client if any;
  • na-valid - if the address is acquired by the client;
  • na-address - the address acquired by the client if any.
  • options - array of received options (only ROSv7)
use-peer-dns (yes | no; Default: yes) Whether to accept the DNS settings advertised by the IPv6 DHCP Server.

Script

It is possible to add a script that will be executed when a prefix or an address is acquired and applied or expires and is removed using DHCP client. There are separated sets of variables that will have the value set by the client depending on prefix or address status change as the client can acquire both and each of them can have a different effect on the router configuration.

Available variables for dhcp-client

  • pd-valid - value - 1 or 0 - if prefix is acquired and it is applied or not
  • pd-prefix - value ipv6/num (ipv6 prefix with mask) - the prefix inself
  • na-valid - value - 1 or 0 - if address is acquired and it is applied or not
  • na-address - value - ipv6 address - the address

Status

Command /ipv6 dhcp-client print detail will show current status of dhcp client and read-only properties listed in table below:

Property Description
duid (string) Auto generated DUID that is sent to the server. DUID is generated using one of the MAC addresses available on the router.
request (list) specifies what was requested - prefix, address or both.
dynamic (yes | no)
expires-after (time) Time when the IPv6 prefix expires (specified by the DHCPv6 server).
invalid (yes | no) Shows whether configuration is invalid.
prefix (IPv6 prefix) Shows received IPv6 prefix from DHCPv6-PD server
status (stopped | searching | requesting... | bound | renewing | rebinding | error | stopping) Shows the status of DHCPv6 Client:
  • stopped - dhcpv6 client is stopped
  • searching - sending "solicit" and trying to get "advertise"
  • requesting - sent "request" waiting for "reply"
  • bound - received "reply". Prefix assigned.
  • renewing - sent "renew", waiting for "reply"
  • rebinding - sent "rebind", waiting for "reply"
  • error - reply was not received in time or some other error ocurred.
  • stopping - sent "release"


To determine what IAID will be used, convert internal ID of an interface on which DHCP client is running from hex to decimal.

For example, DHCP client is running on interface pppoe-out1. To get internal ID use following command 

[admin@t36] /interface> :put [find name="pppoe-out1"]
*15

Now convert hex value 15 to decimal and you get IAID=21

Menu specific commands

Property Description
release (numbers) Release current binding and restart DHCPv6 client
renew (numbers) 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)


Application Examples

Use received prefix for local RA

Consider following setup:

  • ISP is routing prefix 2001:DB8::/62 to the router R1
  • Router R1 runs DHCPv6 server to delegate /64 prefixes to the customer routers CE1 CE2
  • DHCP client on routers CE1 and CE2 receives delegated /64 prefix from the DHCP server (R1).
  • Client routers uses received prefix to set up RA on the local interface


Configuration


R1 

/ipv6 route 
add gateway=fe80::1:1%to-ISP

/ipv6 pool
add name=myPool prefix=2001:db8::/62 prefix-length=64

/ipv6 dhcp-server
add address-pool=myPool disabled=no interface=to-CE-routers lease-time=3m name=server1


CE1 

/ipv6 dhcp-client
add interface=to-R1 request=prefix pool-name=my-ipv6

/ipv6 address
add address=::1/64 from-pool=my-ipv6 interface=to-clients advertise=yes


CE2 

/ipv6 dhcp-client
add interface=to-R1 request=prefix pool-name=my-ipv6

/ipv6 address
add address=::1/64 from-pool=my-ipv6 interface=to-clients advertise=yes


Check the status

After configuration is complete we can verify that each CE router received its own prefix

On server: 

[admin@R1] /ipv6 dhcp-server binding> print 
Flags: X - disabled, D - dynamic 
 #   ADDRESS                                     DUID               IAID SERVER         STATUS 
 1 D 2001:db8:1::/64                             0019d1393536        566 server1        bound
 2 D 2001:db8:2::/64                             0019d1393535        565 server1        bound

On client: 

[admin@CE1] /ipv6 dhcp-client> print 
Flags: D - dynamic, X - disabled, I - invalid 
 #    INTERFACE           STATUS        REQUEST       PREFIX                                     
 0    to-R1               bound         prefix        2001:db8:1::/64  

[admin@CE1] /ipv6 dhcp-client> /ipv6 pool print 
Flags: D - dynamic 
 #   NAME                 PREFIX                              PREFIX-LENGTH
 0 D my-ipv6              2001:db8:1::/64                                64

We can also see that IPv6 address was automatically added from the prefix pool: 

[admin@CE1] /ipv6 address> print 
Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local 
 #    ADDRESS                                     FROM-POOL INTERFACE     ADVERTISE
 0  G 2001:db8:1::1/64                                      to-clients         yes      
..

And pool usage shows that 'Address' is allocating the pool 

[admin@CE1] /ipv6 pool used> print 
POOL         PREFIX                                      OWNER         INFO        
my-ipv6      2001:db8:1::/64                             Address       to-clients

[ Top | Back to Content ]

Retrieved from "https://wiki.mikrotik.com/index.php?title=Manual:IPv6/DHCP_Client&oldid=33941"