mtrp:routing
This is an old revision of the document!
Table of Contents
Routing Behavior
Neighbor Routes
A neighbor route is a destination reachable directly on a registered local path.
Direct neighbors are stored in the neighbor table.
Learned Routes
A learned route is a route advertisement received from another node.
Learned routes are stored in the forwarding table as route candidates. Multiple candidates may exist for the same destination.
Example:
- destination A via next hop B
- destination A via next hop C
- destination A via next hop D
Send-Time Resolution
For unicast frames, MTRP resolves egress in this order:
- use an already-valid explicit egress path if one is present
- try direct neighbor resolution
- try forwarding-table resolution
- mark the frame unroutable if no valid path exists
Preferred Routes
Preferred routes are populated when a forwarded route is actually selected.
This means a node may have many learned routes in the forwarding table while the preferred route table remains empty until forwarding is needed.
Expected Bench Behavior
If all nodes can hear each other directly:
- direct routes usually have the lowest metric
- forwarded alternatives still appear as learned candidates
- direct routes should normally be selected over indirect ones
/var/www/wiki.moshnetworks.com/data/attic/mtrp/routing.1781095907.txt.gz · Last modified: by mosh
