|
|
ZK Mobile 0.8.8 (Default branch)
05-19-2008
The ZK Mobile is a ZK extension that enables ZK applications to run on mobile devices with little programming. With the event-driven components and a markup language, programming is as simple as programming desktops and designing screens is as easy as authoring HTML pages. No JavaME prerequisite is required. License: GNU General Public License (GPL) Changes:|
|
mip6mod(7) Miscellaneous Information Manual mip6mod(7) NAME
mip6mod - Mobile IPv6 STREAMS Module SYNOPSIS
Use the mip6admin utility to start, stop, configure, and manage (see for details). User applications should not use directly. DESCRIPTION
a kernel-resident STREAMS module for Mobile IPv6, implements the Correspondent Node and Home Agent functionality. The STREAMS moudle is responsible for processing and generating all Mobile IPv6 Mobility Header messages: Binding Update (BU), Binding Acknowledgement (BA), Binding Refresh Request (BRR), Binding Error (BE), Home Test Init (HoTI), Care-of Test Init (CoTI), Home Test (HoT), Care-of Test (CoT). The following Mobile IPv6 ICMPv6 messages are handled by the IPv6 Router Advertisement Daemon, Mobile Prefix Solicitation/Advertisement (MPS/MPA), Dynamic Home Agent Discovery Request/Reply (DHAAD Request/Reply). When the system is configured as a Correspondent Node, supports Route Optimization using the Return Routability Procedure. During the Return Routability Procedure, the Correspondent Node and the Mobile Node exchange HoTI/HoT and CoTI/CoT messages in order to establish a binding management key (Kbm) for authenticating the BU and BA messages. You can configure to send out BRR messages when the remaining lifetime of the binding entry drops below the system-configured BRR threshhold value (see for details) When the system is configured as a Home Agent, the IPv6 Router Advertisement Daemon ( ) must alos be running on the system to provide home link prefix information to Multiple home links are supported if the correct home link prefixes are configured on each home link interface. On a Home Agent, IPsec is used to proctect the signalling messages (i.e. BU, BA, HoTI, HoT, MPS, and MPA) between the Mobile Node and the Home Agent. If IPsec ESP is used, the Alternate Care-of Address option must be included within the BU message as the ESP protocol will not be able to protect the Care-of Address (i.e. source address) in the IPv6 header. For troubleshooting purpose, IPsec authentication can be turned off on via to allow Home Agent to accept plain BU messages from the Mobile Node without out IPsec AH or ESP protection. You can configure to include Binding Refresh Advice (BRA) option within the Binding Acknowledgement from the Home Agent when the remaining lifetime of the binding entry drops below the system-configured BRA interval value (see for details). For better performance on high-end systems, multiple instances of can be configured to run on the system processing Mobility Header mes- sages in parallel (see for details). For diagnostics purposes, supports five different levels of diagnostic message logging (i.e. ALERT, ERROR, WARN, INFO, and DEBUG) via the standard mechanism. By default, the system is configured to log at ERROR level. NOTE
provides Mobile IPv6 server functionality (i.e. Home Agent and Correspondent Node). does not provide Mobile Node functionality which is not required on server. AUTHOR
was developed by HP. SEE ALSO
mip6admin(1M), mip6config(1M), rtradvd(1M), syslog(3C) IETF Document Mobility Support in IPv6 IETF Document Using IPsec to Protect Mobile IPv6 Signaling between Mobile Nodes and Home Agents mip6mod(7)