<html><head><meta http-equiv="Content-Type" content="text/html charset=koi8-r"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">If you're using AnnotatedTopologyReader from the example (<a href="http://ndnsim.net/examples.html#node-2-bottleneck-topology-with-custom-forwarding-strategy">http://ndnsim.net/examples.html#node-2-bottleneck-topology-with-custom-forwarding-strategy</a>), then there you can use yet another version of AddRoute:<div><br></div><div>ndn::StackHelper::AddRoute ("src-node-name", "/prefix", "next-hop-node-name", metric); </div><div><br></div><div>You can simply modify weights in the example scenario.</div><div><br></div><div>---</div><div><br></div><div>Regarding GlobalRouting controller. The currently available method CalculateRoutes calculates only one route per destination. I have an extended (and highly experimental) version of it that implements a simple heuristic to calculate alternative routes, but you should be very cautious using this method (it can be very time consuming).<br><div><br></div><div>---</div><div>Alex</div><div><br><div><div>On Mar 4, 2013, at 9:58 AM, Natalya Rozhnova <<a href="mailto:natalya.rozhnova@lip6.fr">natalya.rozhnova@lip6.fr</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi Alex,</div><div> </div><div>It was the first thing I tried to do... I'm a little bit confused with the face numeration. I'm trying the differents settings but the routes are not computed correctly. Probably it's my fault. I'd like to use something similar to the topology from your example here <a href="http://ndnsim.net/_images/aafig-64086469224a310d06aeda159c9fd70f5aebbe08.svg">http://ndnsim.net/_images/aafig-64086469224a310d06aeda159c9fd70f5aebbe08.svg</a> and use different metrics for shortest and longest paths at router 1. Does GlobalRouting allow compute this routes and their costs automatically?</div><div> </div><div>Thanks,</div><div>Natalya</div><div> </div><div>05.03.2013, 00:38, "Alex Afanasyev" <<a href="mailto:alexander.afanasyev@ucla.edu">alexander.afanasyev@ucla.edu</a>>:</div><blockquote><p>Hi Natalya,<br><br>When you're using AddRoute, you can use just a numeric face number, instead of a face object. This face number is based on device id on the Node, so you can just assume that first NetDevice on this Node will correspond to Face 0, next one to face number 1, etc.<br><br>Would this work for you?<br><br>--<br>Alex<br><br>On Mar 4, 2013, at 2:06 AM, Natalya Rozhnova <<a href="mailto:natalya.rozhnova@lip6.fr">natalya.rozhnova@lip6.fr</a>> wrote:</p><blockquote> Hi Alex,<br><br> Could you tell me please how could I configure two or more faces per prefix in FIB entry? Should I use a manual route configuration?<br> I'm actually using the function AddRoute to manually configure FIB entries like ndn::StackHelper.AddRoute(node, prefix, face, metric). But I'm confused how to access to the face from ns3 script?<br><br> Thanks,<br> Natalya</blockquote></blockquote>_______________________________________________<br>ndnSIM mailing list<br><a href="mailto:ndnSIM@lists.cs.ucla.edu">ndnSIM@lists.cs.ucla.edu</a><br>http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim<br></blockquote></div><br></div></div></body></html>