<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;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 12, 2016, at 9:35 AM, Muhammad Hosain Abdollahi Sabet <<a href="mailto:M.AbdollahiSabet@mail.sbu.ac.ir" class="">M.AbdollahiSabet@mail.sbu.ac.ir</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" class="">
<meta name="Generator" content="MS Exchange Server version 6.5.7652.24" class="">
<title class="">Local hub discovery procedure </title>
<div class="">
<!-- Converted from text/plain format --><p class=""><font size="2" class="">Hello everyone,<br class="">
<br class="">
As far as I understood, according to:<br class="">
<a href="http://named-data.net/doc/NFD/current/misc/local-prefix-discovery.html" class="">http://named-data.net/doc/NFD/current/misc/local-prefix-discovery.html</a><br class="">
<a href="http://named-data.net/doc/NFD/current/manpages/ndn-autoconfig.htm" class="">http://named-data.net/doc/NFD/current/manpages/ndn-autoconfig.htm</a><br class="">
<br class="">
When I run ndn-autoconfig, NFD will send an interest to /localhop/ndn-autoconf/hub over a multicast face. After that assuming there is some autoconfig server behind one of the node's multiaccess faces, the node receives a data packet including the face uri of a localhub. </font></p></div></div></blockquote><div>Dear Sabet,</div><br class=""><div>The above correctly describes the basic NDN-native procedure. Just to extend it, as you saw in the documentation, there are two additional stages to help with configuring IP-overlay NDN connectivity. While not yet formally defined, we are also planning to extend the stages to include discovery using mDNS/DNS-SD protocols (<a href="http://redmine.named-data.net/issues/3465" class="">http://redmine.named-data.net/issues/3465</a>). Anecdotally, mDNS queries have higher chances to work than other protocols, even though they utilize the same IP multicast.</div><blockquote type="cite" class=""><div class=""><div class=""><p class=""><font size="2" class="">Then after registering /localhop/ prefix on the very face that it has got from the localhub, the node will again send an interest this time for /localhop/nfd/rib/routable-prefixes and awaits for a data packet including some prefixes which it(interest sender application) can register for publishing data. </font></p></div></div></blockquote><div>Correct, but just to clarify. As of right now, "node" in this sentence is any NDN application that wants to obtain information about routable prefixes. There is an extension of this mechanism (<a href="http://redmine.named-data.net/issues/3145" class="">http://redmine.named-data.net/issues/3145</a>) in which local NFD will be expressing such interests.</div><blockquote type="cite" class=""><div class=""><div class=""><p class=""><font size="2" class="">If I'm wrong some where, please correct me.<br class="">
<br class="">
Right now I have these two multiaccess faces:<br class="">
-<a href="udp4://224.0.23.170:56363" class="">udp4://224.0.23.170:56363</a><br class="">
-<a href="ether://[01:00:5e:00:17:aa]" class="">ether://[01:00:5e:00:17:aa]</a><br class="">
I know the former is IANA assigned, but I don't know the latter. My question are:<br class="">
1- The reason my machine's NFD is not receiving anything form 224.0.23.170 is that this IP is not globally routable, and I don't have any autoconfig server in my local network having this IP and being up and running. Right?<br class=""></font></p></div></div></blockquote><div>224.0.23.170 is a multicast IP address and how far interests sent over such face will propagate depends on your networking environment (e.g., whether or not your WiFI access point allows multicast, whether you're running multicast routing protocol on your routers, etc.).</div><div><br class=""></div>The shorter answer to your question is most likely yes. Not getting any reply most likely mean that you don't have NFD and associated autoconfig server running in your local network.<br class=""><blockquote type="cite" class=""><div class=""><div class=""><p class=""><font size="2" class="">
2- What is the second one? I've checked my host machine's virtual NICs(NFD is on a VM). It's not any of their MACs.<br class=""></font></p></div></div></blockquote><div>This is a multicast Ethernet address. It is not yet assigned, but it is effectively a mapping of 224.0.23.170 to ethernet address range (<a href="https://technet.microsoft.com/en-us/library/cc957928.aspx" class="">https://technet.microsoft.com/en-us/library/cc957928.aspx</a>).</div><br class=""></div><div>Sincerely,</div><div>Alex</div><div><br class=""></div><br class=""></body></html>