1 / 32

Nodes and Packet Forwarding

Nodes and Packet Forwarding. NS2 Chapter 5. 5.1 Node Basics. Node. A node is an OTcl class, but most of its components are TclObjects. All node contain at least the following components An address or an id ( id_ ) monotonically increasing by 1 (from initial value 0)

aikin
Download Presentation

Nodes and Packet Forwarding

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Nodes and Packet Forwarding NS2 Chapter 5

  2. 5.1 Node Basics

  3. Node • A node is an OTcl class, but most of its components are TclObjects. • All node contain at least the following components • An address or an id (id_) monotonically increasing by 1 (from initial value 0) • A list of neighbors (neighbor_) • A list of agents (agent_) • A node type identifier (nodetype_) • A routing module

  4. a label variable instead of a real object Figure 5.1 : Structure of a Unicast Node

  5. In order to enable multicast simulation, we need to set ns [new Simulator -multicast on] Figure 5.2 : Internal Structure of a Multicast Node

  6. 5.2 Node methods: Configuring the Node

  7. Node config • Control functions • Address and port number management, unicast routing functions • Agent management • Adding neighbors

  8. Control functions • $node entry is the first element which will handle packets arriving at that node • $node reset will reset all agents at the node

  9. Address & Port management • $node id returns the node number • $node agent [port] returns the handle of the agent at the specified port • alloc-port returns the next available port number • add-route<destination id>< TclObject>and add-routes, are used by unicast routing to add routes to populate the classifier_ (TclObject is the entry of dmux_) • delete-routes{} takes the id, a list of TclObjects, and a reference to the simulator’s nullagent

  10. Address & Port management • init-routing{} sets the instance variable multiPath_ to be equal to the class variable of the same name • intf-changed{} is invoked by the network dynamics code if a link incident on the node changes state

  11. Agent management • Procedure attach{} will add the agent to its list of agents_, [ assign a port number to the agent and set its source address, set the target of the agent to be its (i.e., the node’s) entry{}, and add a pointer to the port demultiplexer at the node (dmux_) to the agent at the corresponding slot in the dmux_ classifier.) ] • detach{} will remove the agent from agents_

  12. Tracking neighbors • Each node keeps a list of its adjacent neighbors in its instance variable, neighbor_. • Add-neighbor{} adds a neighbor • Neighbors{} returns this list

  13. 5.3 Node Configuration Interface

  14. Node config interface • Simulator::node-config{} accommodates flexible and modular construction of different node definitions within the same base Node class • $ns_ node-config -adhocRouting dsdv • $ns_ node-config -reset • The config command can be broken down into separate lines • $ns_ node-config -addressingType hier • $ns_ node-config -macTrace ON

  15. Table 5.1: Available options for node configuration

  16. 5.4 The Classifier 5.4.1 Address Classifiers 5.4.2 Multicast Classifiers 5.4.3 Multipath Classifier 5.4.4 hash Classifier 5.4.5 Replicator

  17. Classifier • When a node receives a packet, classifier examines the packet’s fields, usually its destination address, and on occasion, its source address • A classifier provides a way to match a packet against some logical criteria and retrieve a reference to another simulation object based on the match results

  18. class Classifier class Classifier : public NsObject { public: ~Classifier(); void recv(Packet*, Handler* h = 0); protected: Classifier(); void install(int slot, NsObject*); void clear(int slot); virtual int command(int argc, const char*const* argv); virtual int classify(Packet *const) = 0; void alloc(int); NsObject** slot_; /* table that maps slot number to a NsObject */ int nslot_; int maxslot_; };

  19. recv() & classify() • When a classifier recv()’s a packet, it hands it to the classify() method. This is defined differently in each type of classifier derived from the base class • The usual format is for the classify() method to determine and return a slot index into the table of slots

  20. Address classifiers • An address classifier is used in supporting unicast packet forwarding • It applies a bitwise shift and mask operation to a packet’s destination address to produce a slot number • The slot number is returned from the classify() method

  21. Multicast classifiers • The multicast classifier classifies packets according to both source and destination (group) addresses • It maintains a (chained hash) table mapping source/group pairs to slot numbers

  22. Multipath classifiers • This object is devised to support equal cost multipath forwarding, where the node has multiple equal cost routes to the same destination, and would like to use all of them simultaneously • This object does not look at any field in the packet. With every succeeding packet, it simply returns the next filled slot in round robin fashion

  23. Hash classifier • This object is used to classify a packet as a member of a particular flow • Hash classifiers use a hash table internally to assign packets to flows

  24. Replicator • Replicator does not use the classify function • Simply uses the classifier as a table of n slots; it overloads the recv() method to produce n copies of a packet, that are delivered to all n objects referenced in the table • Replicator replicates a packet, one for each entry in its table, and delivers the copies to each of the nodes listed in the table. The last entry in the table gets the “original” packet

  25. n0 n1 Port Classifier Multicast Node dmux_ Addr Classifier classifier_ Node entry Node entry dmux_ entry_ entry_ Multicast Classifier classifier_ multiclassifier_ Node – Unicast vs Multicast Unicast Node

  26. 5.5 Routing Module and Classifier Organization 5.5.1 Routing Module 5.5.2 Node Interface

  27. NS routing function blocks • Routing agent • Exchange routing packet with neighbors • Routing logic • Uses the information gathered by routing agents (or the global topology database in the case of static routing) to perform the actual route computation • Classifiers • Use the computed routing table to perform packet forwarding

  28. Figure 5.3: Interaction among node, routing, mobile

  29. Routing module of own • Declare the C++ part of your routing module • Decide which one you’ll inherit, which one you’ll override, and put the interfaces of your own module.em in OTcl

  30. 隨堂抽考 Part 1 問題 Part 2 Hint

  31. 建立topology 1 0 3 2 1.建立上圖的拓樸,節點0與節點3間做TCP(FTP)和UDP的傳輸, 由0到3的傳送,以nam顯示出。 2.顯示出節點2的link id 3.在node2裡加入一個replicatorclassifier並顯示出。

  32. Hint Problem 1 -- 參考/tcl/ex/simple.tcl Problem2-- 使用內建指令 info or Simulator instproc node-to-link {ne1 ne2} { ???? return ????? } Problem 3 -- 利用指令 installNextor install 找到所要加的classifier後,使用指令去做新增動作

More Related