[Ndn-interest] ChronoChat and its default RIB entries

Alex Afanasyev alexander.afanasyev at ucla.edu
Fri Feb 27 15:41:35 PST 2015

Hi Anil,

I think you’re mixing a couple of things.  The face that ChronoChat application uses is just a channel between the application and NFD.  It is normally unix socket face, but it doesn’t really matter, as it is not related to you being able to chat with other people.

Besides having a face that points to a remote chat node, you need to instruct NFD (RIB manager specifically) that specific data can be reached through this face.

In your specific face, you may start by registering /ndn/broadcast prefix for your multicast udp face:

    nfdc register /ndn/broadcast 294

This will tell NFD that data packets with prefix /ndn/broadcast can be retrieved if interest send out through face 294.   You can also register / prefix, which will essentially mean that NFD can try this face to fetch all kind of data packets.


> On Feb 27, 2015, at 1:22 PM, Anil Jangam <anilj.mailing at gmail.com> wrote:
> Hi,
> When I start the ChronoChat client, it creates certain default entries into the RIB as follows.
> /ndn/broadcast/chronochat/chatroom-list route={faceid=294 (origin=0 cost=0 ChildInherit)}
> /ndn/broadcast/ChronoChat/chatroom-e8745dec route={faceid=294 (origin=0 cost=0 ChildInherit)}
> /ndn/broadcast/%F0./chronochat-tmp-identity/f4e4ea96/CHRONOCHAT-INVITATION route={faceid=294 (origin=0 cost=0 ChildInherit)}
> I checked the faceId 294, and it is a non udp/tcp type of face.
> faceid=294 remote=fd://23 local=unix:///run/nfd.sock counters={in={70i 6d 16223B} out={0i 6d 5145B}} local on-demand point-to-point
> In what way I can program the ChronoChat client to use the specific face? may be through some configuration file or so?
> I have configured a face which points to the remote user in the Chat. I guess this local client should be using this interface (257) instead of 294, correct?
> faceid=257 remote=udp4:// <> local=udp4:// <> counters={in={0i 0d 0B} out={0i 0d 0B}} non-local persistent point-to-point
> /anil.
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20150227/0eb2a630/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20150227/0eb2a630/attachment.bin>

More information about the Ndn-interest mailing list