[Nfd-dev] NFD choosing one route only

Mohammad Alhowaidi malhowaidi at gmail.com
Tue Nov 29 08:43:15 PST 2016


Thank you for the reply, so we NFD can't do that in a dynamic way. What if
the route status change after a while, then NFD will not change the route
to select the best-route, right?

Thanks,
Mohammad


On Mon, Nov 28, 2016 at 9:16 PM, Hila Ben Abraham <hila at wustl.edu> wrote:

> Hi Mohammad,
>
> The forwarding strategy is the one making the next hop selection. Under
> the assumption that you are using the default best-route strategy, the next
> hop would be determined by the face cost and not by the link latency.
> According to my understanding, If both links have the same cost then the
> strategy would choose the first face listed in the FIB.
>
> You can use:
> nfdc register -c <cost1> /ndn udp://10.71.102.53
> nfdc register -c <cost2> /ndn udp://10.71.103.63
>
> with cost1>cost2 to achieve your expected behavior when using best-route.
>
> Hila
>
>
> On Mon, Nov 28, 2016 at 8:34 PM Mohammad Alhowaidi <malhowaidi at gmail.com>
> wrote:
>
>> Hello,
>>
>> I setup the nfd to forward the traffic through the following route:
>>
>> nfdc register /ndn udp://10.71.102.53
>> nfdc register /ndn udp://10.71.103.63
>>
>> The first one has a higher latency but it keep forward through the first
>> one, shouldn't it choose the best route ( the second one since it has lower
>> latency )?
>>
>> Thanks,
>> Mohammad
>>
>> _______________________________________________
>> Nfd-dev mailing list
>> Nfd-dev at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20161129/8ff2e551/attachment.html>


More information about the Nfd-dev mailing list