<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi John,<div><br></div><div>I have proceed with your suggestion and new package is on its way to be available soon. I did basic tests, but could have screwed up again with upstart scripts, so be cautious :)</div><div><br></div><div>Small note. ALL_FACES_PREFIXES should be only for /ndn/broadcast</div><div><br></div><div>/ndn/guest should be part of ON_DEMAND_FACES_PREFIXES only on spurs, since only spurs is home for guest users. All other nodes should just have their site's prefix as part of on-demand.</div><div><br></div><div>---</div><div>Alex</div><div><br><div><div>On Aug 14, 2014, at 12:34 PM, John DeHart <<a href="mailto:jdd@seas.wustl.edu">jdd@seas.wustl.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
<br>
Alex and Junxiao,<br>
<br>
Is it possible to expand nfd-autoreg to handle two sets of prefixes,
one for on-demand faces and one for all faces?<br>
Right now in the config file for autoreg config file we have<br>
# Prefixes to register<br>
PREFIXES="/ndn/guest /ndn/broadcast /ndn/edu/memphis"<br>
<br>
What if we had<br>
# Prefixes to register on All faces:<br>
ALL_FACES_PREFIXES="/ndn/guest /ndn/broadcast"<br>
<br>
# Prefixes to register just on on-demand faces:<br>
ON_DEMAND_FACES_PREFIXES="/ndn/edu/memphis"<br>
<br>
on-demand faces would get both sets.<br>
Non-on-demand faces would get just ALL_FACES_PREFIXES.<br>
<br>
John<br>
<br>
<br>
<div class="moz-cite-prefix">On 8/14/14, 1:10 PM, Alex Afanasyev
wrote:<br>
</div>
<blockquote cite="mid:B441BA46-5B48-4766-A04A-923686539566@ucla.edu" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>I have proposed that before, but will repeat. I don't think
that broadcast prefixes (and setting the strategy) is what NLSR
should do. At most, this should be some other routing protocol.
What we could do instead is to write a tiny little daemon like
nfd-autoreg, which job would be just to register /ndn/broadcast
for every created face (not just on-demand ones). May be we can
ignore application faces, though it doesn't matter for NDN
testbed much.</div>
<div><br>
</div>
<div>---</div>
<div>Alex</div>
<br>
<div>
<div>On Aug 14, 2014, at 9:55 AM, Junxiao Shi <<a moz-do-not-send="true" href="mailto:shijunxiao@email.arizona.edu">shijunxiao@email.arizona.edu</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="ltr">Hi John
<div><br>
</div>
<div>fib.max-faces-per-prefix is the maximum number of
Routes with same Name prefix that NLSR will install to the
RIB.</div>
<div>The parameter starts with "fib." due to historical
reason; it concerns what NLSR would install to the RIB,
not FIB.<br>
</div>
<div><br>
</div>
<div>I suggest setting this parameter to 60, so that
expansions in the near future are also covered.</div>
<div>When there are no more than 5 backbone links, setting
it to 5 or 60 has same effect.</div>
<div><br>
</div>
<div>This short term solution would stop working when a HUB
has more than 60 backbone links, but this day is unlikely
to come within one year.</div>
<div><br>
</div>
<div>Yours, Junxiao<br>
<div class="gmail_extra">
<br>
<br>
<div class="gmail_quote">On Thu, Aug 14, 2014 at 9:46
AM, John DeHart <span dir="ltr"><<a moz-do-not-send="true" href="mailto:jdd@seas.wustl.edu" target="_blank">jdd@seas.wustl.edu</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> <br>
Junxiao,<br>
<br>
Ahh. I was thinking of the
fib.max-faces-per-prefix as a limit on all faces
not just<br>
ones that NLSR is concerned with. <br>
<br>
In the testbed right now we have 5 nodes that<br>
each have 5 links to other nodes. Those are the
most connected nodes.<br>
So, if we set the fib.max-faces-per-prefix for
NLSR to >= 5 we should be ok.<br>
Right?<span><font color="#888888"><br>
<br>
John</font></span>
<div><br>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
_______________________________________________<br>
Operators mailing list<br>
<a moz-do-not-send="true" href="mailto:Operators@lists.named-data.net">Operators@lists.named-data.net</a><br>
<a class="moz-txt-link-freetext" href="http://lists.named-data.net/mailman/listinfo/operators">http://lists.named-data.net/mailman/listinfo/operators</a><br>
</blockquote>
</div>
<br>
</blockquote>
<br>
</div>
</blockquote></div><br></div></body></html>