|void (TM_CODE_FAR * tt6DevAddrNotifyFunc)||(|
|unsigned int multiHomeIndex,|
|struct sockaddr_storage * ipv6AddrPtr,|
This is the type definition for the IPv6-specific address notification function. A function of this type may be registered with tfNgOpenInterface() or tfNgConfigInterface(). This allows the user to be notified of IPv6-specific address related events, as described below.
- A handle to the interface on which the event occurred.
- The multihome that the specified address is configured at.
- The IPv6 address that underwent the specified event.
- The IPv6 address event. See below.
IPv6 Address Configuration Events
- Configuration of the IPv6 address has been started. Duplicate Address Detection is being performed on the tentative address.
- Duplicate Address Detection failed. A different node is already using the tentative address we tried to configure, therefore configuration failed.
- Duplicate Address Detection succeeded. Configuration of the IPv6 address on the interface completed successfully.
- The Treck stack detected that a different node is using one of your IPv6 addresses that was successfully configured (i.e. for which the TM_6_DEV_ADDR_CONFIG_COMPLETE event has occurred). It is up to the user to specify what recovery, if any, is performed when this event occurs. ([RFC 2462])
- An auto-configured IPv6 address has transitioned state from deprecated to preferred.
- An auto-configured IPv6 address has transitioned state from preferred to deprecated.
- An auto-configured IPv6 address has transitioned state to invalid, and has been unconfigured from the interface.
- An DHCPv6 address has been released and unconfigured from the interface.
- An DHCPv6 address has been declined and not configured on the interface.
- DHCPv6 client does not have the key requested by the server to complete the authentication process.
- DHCPv6 client has the key requested by the server, but it has expired and the client is not able to complete the authentication process.