Distributed Routing Protocol in Wireless Network Simulation Oct 9, 2001

Wireless Network Routing in ns IP: decide the next hop by looking up the routing table Routing protocol: DSDV, DSR, TORA, AODV MAC: 802.11 PHY: Propagation Model Free Space Model, Two Way Ground Reflection Model, Shadowing Model

Problem in Distributed Simulation TCP/Source N1 ? TCP/Sink N2 N3 N4 proxy proxy Federate A Federate B How to route? Can proxy work? No. We don’t know where we can put the proxies. (unlike wired) How to refer the remote agent?

Solution – Distributed routing protocol TCP/Source N1 ? TCP/Sink N2 N3 N4 gw gw Federate A Federate B Simulation behaves just like in real network A gateway represents a neighboring partition. GWs is a special mobilenode, no position associated. A lot of GW pairs.

Cont. Routing updates Cross boundary data exchange A mobilenode sends the routing messages to all the partitions if applicable through GWs. A mobile node’s routing entry records which GW to go through if needed for the next hop. Cross boundary data exchange The packet containing the source node position will be sent to local GW without loss. The local GW exchanges data with remote GW through RTI Remote GW pretends to be the source node to sends packet to the target node.

Cont Node object reference with IP address Agent object reference with IP address + Port # Avoid invalid object handle/id across/pointer across address space Pro: A federate only need to know its own partition. No knowledge about other partitions is required.