Go to main content

Configuring and Managing Network Components in Oracle® Solaris 11.4

Exit Print View

Updated: December 2019

Configuring an IPv6 Token

The 64-bit interface ID of an IPv6 address is also referred to as a token. By default, autoconfiguration creates the token based on the interface's MAC address.

However, you can create a token that is not based on the MAC address. Instead, you create a 64-bit hexadecimal number as the interface ID. This token remains assigned to the interface, even when a card is replaced.

IPv6 tokens are another alternative to use on systems whose interfaces are routinely swapped. Just like static addresses, they can serve as alternatives to using normal autoconfiguration. See Configuring IPv6 Interfaces.

How to Configure a User-Specified IPv6 Token

Before You Begin

Ensure that your role has the appropriate rights profile to perform this procedure. See Using Rights Profiles to Perform Network Configuration.

  1. Verify that the interface that you want to configure with a token exists and that no IPv6 addresses are configured on that interface.
  2. Configure each interface that has a user-specified interface ID (token).
    $ ipadm create-addr -T addrconf -i token interface

    The token you create must be in the following format:


    Note -  After you create the address object with the token, you can no longer modify the token.
Example 6  Configuring a User-Specified Token on an IPv6 Interface

The following example shows how to configure net0 with an IPv6 address and a token.

$ ipadm show-if
lo0      loopback   ok       yes        ---
net0     ip         ok       yes        ---

$ ipadm show-addr
lo0/v4       static     ok

$ ipadm create-addr -T addrconf -i ::1a:2b:3c:4d/64 net0
$ ipadm show-addr
lo0/v6       static     ok      ::1/128
net0/v6      addrconf   ok      2001:db8:1a:2b:3c:4d/10
net0/v6a     addrconf   ok      2001:db8:39f0:1:1a:2b:3c:4d/64

After the token is configured, the address object net0/v6 has both a link-local address, as well as an address with 1a:2b:3c:4d configured for its interface ID.

See Also