Skip to content
This repository has been archived by the owner on Jan 28, 2021. It is now read-only.

Implement Neighbor Set #88

Open
jeandudey opened this issue Apr 28, 2020 · 0 comments
Open

Implement Neighbor Set #88

jeandudey opened this issue Apr 28, 2020 · 0 comments

Comments

@jeandudey
Copy link
Member

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>
 */
typedef struct {
    /**
     * @brief   An IP address of the neighboring router.
     */
    ipv6_addr_t address;
    /**
     * @brief   Indicates whether the link to the neighbor is bidirectional.
     */
    uint8_t state;
    /**
     * @brief   Indicates the time at which the Neighbor.State should be updated:
     */
    timex_t timeout; 
    /**
     * @brief   The interface on which the link to the neighbor was established.
     */
    gnrc_netif_t *interface;
    aodvv2_seqnum_t ack_seqnum;
    aodvv2_seqnum_t heard_rerr_seqnum;
} aodvv2_neighbor_t;

Further reading

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Routing
  
To do
Development

No branches or pull requests

1 participant