Is it possible to use static routing in conjunction with MANET?

Is it possible to use static routing in conjunction with MANET?

Steps 1. It is possible to use static routing with popular MANET routing protocols, such as AODV and OLSR. The exception is DSR, which is a source routing protocol and does not consult IP forwarding tables for routing. Also OSPFv3-MANET is an extension protocol, and since OSPFv3 is a legacy routing protocol, it is even more seamlessly used with the static routing protocol.2. Each host and router node has an attribute for specifying the static routing table. On a host, this attribute is specified under: IP/IP Host Parameters/Static Routing Table (at the same hierarchy, an IPv6 equivalent of this attribute also exists). On a router, the attribute can be found under: IP/IP Routing Parameters/Static Routing Table. The IPv6 equivalent for the routers is under: IP/IPv6 Parameters/Static Routing Table.3. A static routing entry needs the following basic specifications:Destination IP AddressDestination Subnet MaskNext HopTo use static routing in MANET environments, starting from the source node, one can specify the destination IP Address/Subnet Mask and the IP address of the next hop node. This scheme works fine until one reaches the last hop, i.e. the node right before the destination itself. To understand why this configuration does not work for the last hop, consider the following situation:Topology: A -- B -- C -- D. Let prefixes be: A: 1.1.1.1, B: 2.2.2.2, C: 3.3.3.3, D: 4.4.4.4. Let us also assume that all nodes run OLSR and that A is the source and D is the destination.A static route on A can be configured as follows: Destination 4.4.4.4/32, next hop 2.2.2.2. This works, because the next hop 2.2.2.2 can be discovered by OLSR independently and recursive routing table lookup tells us how to reach this next hop. From there, we also know how to reach the destination through the next hop.For the last hop though, if we did this, there is a problem. Consider the static routing configuration at C: Destination 4.4.4.4/32, next hop 4.4.4.4. Now if destination == next hop, next hop can never get resolved! Even though C and D run OLSR, OLSR route is rejected in favor of static route and recursive lookup does not tell us how to reach 4.4.4.4. In this situation, we simply cannot do anything BUT to enforce the routing as follows: Static route: Destination 4.4.4.4 next hop IF0, where IF0 is the symbolic name of the interface. Now, we simply enforce the interface and hope that traffic automatically reaches the destination.4. One of the primary reasons static routing specification by IP address does not work for the last hop in MANET is the absence of directly connected routes. In wireline situations, the last hop router would have a direct connection to the host and a directly connected route would resolve the next hop of the static route. But in MANET situations, all hosts can potentially carry different prefixes, and no directly connected route between the 2 hosts with the same subnet can be expected to exist. Thus users have to ensure to specify the next hop by interface rather than the IP address for the last hop.

Protocols->MANET