[Ndn-interest] ChronoChat and its default RIB entries

[Anil Jangam]

Hi,

I could start two ChronoChat processes from same host, and upon creating
and joining the same chatroom, they are able to chat with each other.
However, I think this message transaction is not going over the IP network,
and I am not able to see any messages on ndndump. What way we can trace
these messages using tcpdump?

I am also getting an Warning message, "Warning: no connection to hub or hub
does not support prefix autoconfig".. I am not sure what this means.

Again, I want to run this chat across two remote hosts, and the problem
mentioned earlier still exist. How can I force ChronoChat to use specific
face Id instead of picking up the default one.

Can someone please comment on this?

/anil


On Fri, 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://224.0.23.170:56363 local=udp4://
> 133.164.60.154:56363 counters={in={0i 0d 0B} out={0i 0d 0B}} non-local
> persistent point-to-point
>
>
> /anil.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20150227/0ecf9723/attachment.html>