Scribd
Upload
46 views

Action When Where Layer: S 76.000000000 - 98 - AGT - 1812 CBR 32 (0 0 0 0) - (98:0 0:0 32 0)

The document provides information for interpreting trace files from network simulator 2 (NS-2). It explains that each line contains information about a packet including the action taken, time, node, layer, sequence number, type, size, MAC addresses, IP addresses, TTL, and TCP sequence numbers. It provides examples of lines from a trace file and their interpretations, such as a line showing a CBR packet being sent from node 98 to node 0 at time 76.0 seconds. Another example line shows a GPSR routing packet being received by node 9 from node 8. The document helps understand what each field in the trace file lines represents.

Uploaded by

Mujahidah Achiru
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
46 views

Action When Where Layer: S 76.000000000 - 98 - AGT - 1812 CBR 32 (0 0 0 0) - (98:0 0:0 32 0)

The document provides information for interpreting trace files from network simulator 2 (NS-2). It explains that each line contains information about a packet including the action taken, time, node, layer, sequence number, type, size, MAC addresses, IP addresses, TTL, and TCP sequence numbers. It provides examples of lines from a trace file and their interpretations, such as a line showing a CBR packet being sent from node 98 to node 0 at time 76.0 seconds. Another example line shows a GPSR routing packet being received by node 9 from node 8. The document helps understand what each field in the trace file lines represents.

Uploaded by

Mujahidah Achiru
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

ACTION: [s|r|D|f]: s -- sent, r -- received, D -- dropped,f -forwarded

WHEN: the time when the action happened


WHERE: the node where the action happened
LAYER: AGT -- application,
RTR -- routing,
LL -- link layer (ARP is done here)
IFQ -- outgoing packet queue (between link and mac layer)
MAC -- mac,
PHY -- physical
flags:
SEQNO: the sequence number of the packet
TYPE: the packet type
cbr -- CBR data stream packet
DSR -- DSR routing packet (control packet generated by routing)
RTS -- RTS packet generated by MAC 802.11
ARP -- link layer ARP packet
SIZE: the size of packet at current layer, when packet goes down,
size increases, goes up size decreases
[a b c d]: a -- the packet duration in mac layer header
b -- the mac address of destination
c -- the mac address of source
d -- the mac type of the packet body
flags:
[......]: [
source node ip : port_number
destination node ip (-1 means broadcast) : port_number
ip header ttl
ip of next hop (0 means node 0 or broadcast)
]
So if you have a line like this

s 76.000000000 _98_ AGT 1812 cbr 32 [0 0 0 0] - [98:0 0:0 32 0]


in your trace file.
You should interpret it as
Application 0 (port number) on node 98 sent a CBR packet whose ID is 1812 and size
is 32 bytes, attime 76.0 second, to application 0 on node 0 with TTL is 32 hops. The next
hop is not decided yet.
Similarly, You should be able to interpret a line such as this:
r 0.010176954 _9_ RTR 1 gpsr 29 [0 ffffffff 8 800] - [8:255 -1:255
32 0]
as
The routing agent on node 9 received a GPSR broadcast (mac address 0xf, and ip address
is -1, either of them means broadcast) routing packet whose ID is 1 and size is 29
bytes, at time 0.010176954 second, from node 8 (both mac and ip addresses are 8), port
255 (routing agent).
If you choose to play safe by making use of Tracegraph, then <this> post might help you.

Update:
Recently, I chanced to read <this manual> by Eitman Altman and manual is well
organised for intermediate learners in ns2. I have extraced the ns2 trace file part from
that and presented it below.
r 40.639943289 _1_ AGT - 1569 tcp 1032 [a2 1 2 800] - [0:0 1:0 32 1] [35 0] 2 0
* The first field is a letter that can have the values r,s,f,D for
received,sent,forwarded and dropped, respectively.It can also be < for giving a
location or a movement indication.
* The second field is the time.
* The third field is the node number.
* The fourth field is MAC to indicate if the packet concerns a MAC layer, it is AGT to
indicate the transport layer(e.g. tcp) packet, or RTR if it concerns the routed packet. It
can also be IFQ to indicate events related to the interference priority queue(like drop of
packets).
* After the dashes come the global sequence number of the packet(this is not the tcp
sequence number).
* At the next field comes more information on the packet type(eg. tcp,ack or udp).
* Then comes the packet size in bytes.
* The 4 numbers in the first square brackets concern the mac layer information. The first
hexadecimal number,a2(which equals 162 in decimal) specifies the expected time in
seconds to send this data packet over the wireless channel. The second number,1,
stands for the MAC-id of the sending node, and the third,2, is that of the receiving node.
The fourth number,800, specifies that the MAC type is ETHERTYPE_IP.
* The next numbers in the second square brackets concern the IP source and destination
addresses, then the ttl(Time To Live) of the packet(in our case 32),
* The third bracket concern the tcp information: its sequence number and the
acknowledgment number.

You might also like