Icmpv6EchoRequestMsg
classICMPv6 Echo Request packet (RFC2463: Section 4). Data is attached through encapsulation (see Icmpv6.cc)
Inheritance diagram
The following diagram shows inheritance relationships for this type. Unresolved types are missing from the diagram.
Extends
Name | Type | Description |
---|---|---|
Icmpv6Header | class |
Represents an ICMPv6 packet. |
Fields
Name | Type | Description |
---|---|---|
type | Icmpv6Type |
1 byte |
code | int |
set to 0. |
identifier | int |
identifier to aid in matching Echo replies. May be Zero |
seqNumber | int |
sequence number to aid in matching Echo replies. May be Zero Data is attached through encapsulation. See Icmpv6.cc |
chunkLength | b | |
chksum | int |
int code; // 1 byte //TODO: this should be specific to different ICMP types. |
crcMode | CrcMode |
4 bytes 'type' specific values |
mutable | bool | |
complete | bool | |
correct | bool | |
properlyRepresented | bool | |
rawBin | string[] | |
rawHex | string[] | |
tags | RegionTagSet::cObjectRegionTag[] |
Source code
// // ICMPv6 Echo Request packet (RFC2463: Section 4). // Data is attached through encapsulation (see Icmpv6.cc) // class Icmpv6EchoRequestMsg extends Icmpv6Header { type = ICMPv6_ECHO_REQUEST; int code = 0; //set to 0. int identifier; // identifier to aid in matching Echo replies. May be Zero int seqNumber; // sequence number to aid in matching Echo replies. May be Zero //Data is attached through encapsulation. See Icmpv6.cc }File: src/inet/networklayer/icmpv6/Icmpv6Header.msg