You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 28, 2021. It is now read-only.
The neighbor set contains information about neighboring AODVv2 routers, this differs from the NIB on RIOT-OS which is specific to link local nodes and NDP itself.
Having a complete implementation could give more benefits as outlined in the draft, although not explicitly needed.
I'm currently working on the Local Route Set, if anyone is willing to work on this feel free to comment here and take a look.
A possible implementation of the entries would look like this:
/** * @brief Neighbor Set entry * * @see <a href="https://tools.ietf.org/html/draft-perkins-manet-aodvv2-03#section-4.3"> * draft-perkins-manet-aodvv2-03, Section 4.3. Neighbor Set * </a> */typedefstruct {
/** * @brief An IP address of the neighboring router. */ipv6_addr_taddress;
/** * @brief Indicates whether the link to the neighbor is bidirectional. */uint8_tstate;
/** * @brief Indicates the time at which the Neighbor.State should be updated: */timex_ttimeout;
/** * @brief The interface on which the link to the neighbor was established. */gnrc_netif_t*interface;
aodvv2_seqnum_tack_seqnum;
aodvv2_seqnum_theard_rerr_seqnum;
} aodvv2_neighbor_t;
The neighbor set contains information about neighboring AODVv2 routers, this differs from the NIB on RIOT-OS which is specific to link local nodes and NDP itself.
Having a complete implementation could give more benefits as outlined in the draft, although not explicitly needed.
I'm currently working on the Local Route Set, if anyone is willing to work on this feel free to comment here and take a look.
A possible implementation of the entries would look like this:
Further reading
The text was updated successfully, but these errors were encountered: