Information repositories

As a derivate of the classical link-state algorithm, OLSR maintains state by keeping a variety of databases of information. These information repositories are updated upon processing received control messages and the information stored is used when generating such messages. Here follows a brief look at the different information repositories used in core OLSR.

Multiple Interface Association Information Base

This dataset contains information about nodes using more than one communication interface. All interface addresses of such nodes are stored here.

Link Set

This repository is maintained to calculate the state of links to neighbors. This is the only database that operates on non-main-addresses as it works on specific interface-to-interface links.

Neighbor Set

All registered one-hop neighbors are recorded here. The data is dynamically updated based on information in the link set. Both symmetric and asymmetric neighbors are registered.

2-hop Neighbor Set

All nodes, not including the local node, that can be reached via an one-hop neighbor is registered here. Notice that the two hop neighbor set can contain nodes registered in the neighbor set as well.

MPR Set

All MPRs selected by the local node is registered in this repository. The MPR concept is explained in section 3.4.

MPR Selector Set

All neighbors that have selected this node as a MPR are recorded in this repository.

Topology Information Base

This repository contains information of all link-state information received from nodes in the OLSR routing domain.

Duplicate set

This database contains information about recently processed and forwarded messages.