|
View Poll Results: Who Makes Your (Primary) Mobile Phone? | |||
Nokia | 23 | 30.67% | |
HTC | 12 | 16.00% | |
Apple | 11 | 14.67% | |
Samsung | 11 | 14.67% | |
Motorola | 4 | 5.33% | |
RIM (Blackberry) | 4 | 5.33% | |
Ericsson | 3 | 4.00% | |
Sony | 3 | 4.00% | |
LG | 2 | 2.67% | |
Other | 1 | 1.33% | |
Sagem (quadphonic) | 1 | 1.33% | |
Dell | 0 | 0% | |
Mitsubishi | 0 | 0% | |
NEC | 0 | 0% | |
Palm | 0 | 0% | |
Panasonic | 0 | 0% | |
Sanyo | 0 | 0% | |
Sharp | 0 | 0% | |
Voters: 75. This poll is closed |
|
|
mip6d(1) Mobile IPv6 and NEMO Daemon mip6d(1) NAME
mip6d - UMIP Mobile IPv6 and NEMO Basic Support protocol implementation SYNOPSIS
mip6d [options] DESCRIPTION
Mobile IPv6 and NEMO Basic Support implementation OPTIONS
-V, --version Display version information and copyright -?, -h, --help Display this help text -c <file> Read configuration from <file>. If option is not present, default path (/etc/mip6d.conf) is used. These options override values read from config file: -d <number> Set debug level (0-10) -C, --correspondent-node Node is CN -H, --home-agent Node is HA -M, --mobile-node Node is MN SIGNALS
The following signals can be sent to the daemon: SIGHUP Reload the configuration. See mip6d.conf(5) for information on supported option reload. SIGINT, SIGTERM Terminates the daemon operation. FILES
/etc/mip6d.conf SEE ALSO
mip6d.conf(5), mipv6(7), RFC6275: Mobility Support in IPv6 RFC3776: Using IPsec to Protect Mobile IPv6 Signaling Between Mobile Nodes and Home Agents RFC4877: Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture RFC3963: Network Mobility (NEMO) Basic Support Protocol May 16, 2005 mip6d(1)