man/man8/ip-token.8

   1 .TH IP\-TOKEN 8 "28 Mar 2013" "iproute2" "Linux"
   2 .SH "NAME"
   3 ip-token \- tokenized interface identifier support
   4 .SH "SYNOPSIS"
   5 .sp
   6 .ad l
   7 .in +8
   8 .ti -8
   9 .B ip token
  10 .RI " { " COMMAND " | "
  11 .BR help " }"
  12 .sp
  13
  14 .ti -8
  15 .BR "ip token" " { " set " } "
  16 .IR TOKEN
  17 .B dev
  18 .IR DEV
  19
  20 .ti -8
  21 .BR "ip token" " { " get " } "
  22 .B dev
  23 .IR DEV
  24
  25 .ti -8
  26 .BR "ip token" " { " list " }"
  27
  28 .SH "DESCRIPTION"
  29 IPv6 tokenized interface identifier support is used for assigning well-known
  30 host-part addresses to nodes whilst still obtaining a global network prefix
  31 from Router advertisements. The primary target for tokenized identifiers are
  32 server platforms where addresses are usually manually configured, rather than
  33 using DHCPv6 or SLAAC. By using tokenized identifiers, hosts can still
  34 determine their network prefix by use of SLAAC, but more readily be
  35 automatically renumbered should their network prefix change [1]. Tokenized
  36 IPv6 Identifiers are described in the draft
  37 [1]: <draft-chown-6man-tokenised-ipv6-identifiers-02>.
  38
  39 .SS ip token set - set an interface token
  40 set the interface token to the kernel. Once a token is set, it cannot be
  41 removed from the interface, only overwritten.
  42 .TP
  43 .I TOKEN
  44 the interface identifier token address.
  45 .TP
  46 .BI dev " DEV"
  47 the networking interface.
  48
  49 .SS ip token get - get the interface token from the kernel
  50 show a tokenized interface identifier of a particular networking device.
  51 .B Arguments:
  52 coincide with the arguments of
  53 .B ip token set
  54 but the
  55 .I TOKEN
  56 must be left out.
  57 .SS ip token list - list all interface tokens
  58 list all tokenized interface identifiers for the networking interfaces from
  59 the kernel.
  60
  61 .SH SEE ALSO
  62 .br
  63 .BR ip (8)
  64
  65 .SH AUTHOR
  66 Manpage by Daniel Borkmann