How to Analyze Network Protocols, Learn More >>

Being able to support more than 300 protocols in the latest version, Capsa Network Sniffer make it easy to analyze protocols in network and understand what is happening.

Recommend Network Analysis Software >>


RFC 2002 http://tools.ietf.org/html/rfc2002
RFC 2290 http://tools.ietf.org/html/rfc2290
RFC 2344 http://tools.ietf.org/html/rfc2344

The Mobile IP protocol enables nodes to move from one IP subnet to another. Each mobile node is always identified by its home address, regardless of its current point of attachment to the Internet. While situated away from its home, a mobile node is also associated with a care-of address, which provides information about its current point of attachment to the Internet. The protocol allows registration of the care-of address with a home agent. The home agent sends datagrams destined for the mobile node through a tunnel to the care-of address. After arriving at the end of the tunnel, each datagram is then delivered to the mobile node. It can be used for mobility across both homogeneous and heterogeneous media. Mobile IP defines a set of new control messages, sent with UDP, Registration Request and Registration Reply.
The IP packet consists of the IP source and destination addresses, followed by the UDP source and destination ports, followed by the Mobile IP fields. Mobile IP packets can be either registration request or registration reply.
The format of the Mobile IP registration request message is shown in the following illustration:

8
9
10
11
12
13
14
15
16
Octet
Type
S
B
D
M
G
V
T
Rsv
2
Lifetime
4
Home address
8
Home agent
12
Care of address
16
Identification
20
Extensions …
...
Mobile IP registration request message structure
 

Type
1 signifies a registration request.

S
Simultaneous bindings. When set, the mobile node is requesting that the home agent retain its prior mobility bindings.

B
Broadcast datagrams. When set, the mobile node requests that the home agent tunnel to it any broadcast datagrams that it receives on the home network.

D
Decapsulation by mobile node. When set, the mobile node will itself decapsulate datagrams which are sent to the care-of address. In other words, the mobile node is using a co-located care-of address.

M
Minimal encapsulation. When set, the mobile node requests that its home agent use minimal encapsulation for datagrams tunneled to the mobile node.

G
GRE encapsulation. When set, the mobile node requests that its home agent use GRE encapsulation for datagrams tunneled to the mobile node.

V
The mobile node requests that its mobility agent use Van Jacobson header compression over its link with the mobile node.

T
When set, the mobile node asks its home agent to accept a reverse tunnel from the care-of address. Mobile nodes using a foreign agent care-of address ask the foreign agent to reverse-tunnel its packets.

Rsv
Reserved bit, set to zero.

Lifetime
The number of seconds remaining before the registration expires.

Home address
IP address of the mobile node.

Home agent

IP address of the mobile node’s home agent.

Care-of address

IP address for the end of the tunnel.

Identification
A 64-bit number, constructed by the mobile node, used for matching registration requests with registration replies, and for protecting against replay attacks of registration messages.

Extensions
The fixed portion of the registration request is followed by one or more of the extensions listed in Section 3.5 of RFC2002. The Mobile-Home Authentication Extension must be included in all registration requests.
The format of the Mobile IP registration reply message is shown in the following illustration:

8 16 32 Octets
Type
Code
Lifetime
4
Home address 8
8
Home agent 12
12
Identification 20
20
Extensions …
...
Mobile IP registration reply message structure
 

Type
3 indicates a registration reply.

Code
A value indicating the result of the Registration Request. Values may be as follows:
Registration successful:
0
1
Registration accepted.
Registration accepted, but simultaneous mobility bindings unsupported.
Registration denied by the foreign agent:
64
65
66
67
68
69
70
71
72
73
Reason unspecified.
Administratively prohibited.
Insufficient resources.
Mobile node failed authentication.
Home agent failed authentication.
Requested Lifetime too long.
Poorly formed Request.
Poorly formed Reply.
Requested encapsulation unavailable.
Requested Van Jacobson compression unavailable.
Service denied by the foreign agent:
74
75
76
Requested reverse tunnel unavailable.
Reverse tunnel is mandatory and T bit not set.
Mobile node too distant
Registration denied by the home agent:
80
81
82
88
Home network unreachable (ICMP error received).
Home agent host unreachable (ICMP error received).
Home agent port unreachable (ICMP error received).
Home agent unreachable (other ICMP error received).
Service denied by the home agent:
137
138
139
Requested reverse tunnel unavailable.
Reverse tunnel is mandatory and T bit not set.
Requested encapsulation unavailable.

Lifetime
If the Code field indicates that the registration was accepted, the Lifetime field is set to the number of seconds remaining before the registration expires. A value of zero indicates that the mobile node has been deregistered. A value of 0xffff indicates infinity. If the Code field indicates that the registration was denied, the contents of the Lifetime field are unspecified and are ignored on reception.

Vulnerabilities for this protocol (from CVE)

CVE ID Protocol Source Port Targetport

TCP/IP Protocols:

AHARP/RARPATMPBGP-4COPSDCAPDHCPDNS
DVMRPEGPEIGRPESPFANPFingerFTPHSRP
HTTPICMPICMPv6IGMPIGRPIMAP4IPIPDC
IPv6ISAKMPL2FL2TPLDAPMARSMobile IPNARP
NetBIOS/IPNHRPNTPOSPFPIMPOP3PPTPRadius
RIP2RIPng for IPv6RLOGINRSVPRTSPRUDPS-HTTPSCTP
SLPSMTPSNMPSOCKS V5TACACSTALITCPTELNET
TFTPUDPVan JacobsonVRRPWCCPX-WindowXOT