12.07.2015 Views

The ns Manual (formerly ns Notes and Documentation)1 - NM Lab at ...

The ns Manual (formerly ns Notes and Documentation)1 - NM Lab at ...

The ns Manual (formerly ns Notes and Documentation)1 - NM Lab at ...

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Packet info <strong>at</strong> "Applic<strong>at</strong>ion level" <strong>The</strong> packet inform<strong>at</strong>ion <strong>at</strong> applic<strong>at</strong>ion level co<strong>ns</strong>ists of the type of applic<strong>at</strong>ion like ARP,TCP, the type of adhoc routing protocol like DSDV, DSR, AODV etc being traced. This field co<strong>ns</strong>ists of a leading "-P"<strong>and</strong> list of tags for different applic<strong>at</strong>ion is listed as below:-P arp Address Resolution Protocol. Details for ARP is given by the following tags:-Po: ARP Request/Reply-Pm: src mac address-Ps: src address-Pa: dst mac address-Pd: dst address-P dsr This denotes the adhoc routing protocol called Dynamic source routing. Inform<strong>at</strong>ion on DSR is represented bythe following tags:-Pn: how many nodes traversed-Pq: routing request flag-Pi: route request sequence number-Pp: routing reply flag-Pl: reply length-Pe: src of srcrouting->dst of the source routing-Pw: error report flag ?-Pm: number of errors-Pc: report to whom-Pb: link error from linka->linkb-P cbr Co<strong>ns</strong>tant bit r<strong>at</strong>e. Inform<strong>at</strong>ion about the CBR applic<strong>at</strong>ion is represented by the following tags:-Pi: sequence number-Pf: how many times this pkt was forwarded-Po: optimal number of forwards-P tcp Inform<strong>at</strong>ion about TCP flow is given by the following subtags:-Ps: seq number-Pa: ack number-Pf: how many times this pkt was forwarded-Po: optimal number of forwardsThis field is still under development <strong>and</strong> new tags shall be added for other applic<strong>at</strong>io<strong>ns</strong> as they get included along theway.16.1.8 Gener<strong>at</strong>ion of node-movement <strong>and</strong> traffic-connection for wireless scenariosNormally for large topologies, the node movement <strong>and</strong> traffic connection p<strong>at</strong>ter<strong>ns</strong> are defined in separ<strong>at</strong>e files for convinience.<strong>The</strong>se movement <strong>and</strong> traffic files may be gener<strong>at</strong>ed using CMU’s movement- <strong>and</strong> connection-gener<strong>at</strong>ors. In this section weshall describe both separ<strong>at</strong>ely.MobileNode MovementSome examples of node movement files may be found in ~<strong>ns</strong>/tcl/mobility/scene/scen-670x670-50-600-20-*. <strong>The</strong>se filesdefine a topology of 670 by 670m where 50 nodes move with a speed of 20m/s with pause time of 600s. each node is assigned160

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!