<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></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 27, 2015, at 3:08 PM, Anil Jangam <<a href="mailto:anilj.mailing@gmail.com" class="">anilj.mailing@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi,<div class=""><br class=""></div><div class="">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?<div class=""><br class=""></div><div class="">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. </div></div></div></div></blockquote><div><br class=""></div><div>You have this message, as the current ChronoChat implementation has some assumptions about the environment. However, this should not prevent you from chatting.</div><div><br class=""></div><div>—</div><div>Alex</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class="">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. </div><div class=""><br class=""></div><div class="">Can someone please comment on this?</div><div class=""><br class=""></div><div class="">/anil</div><div class=""><br class=""></div></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Fri, Feb 27, 2015 at 1:22 PM, Anil Jangam <span dir="ltr" class=""><<a href="mailto:anilj.mailing@gmail.com" target="_blank" class="">anilj.mailing@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Hi,<div class=""><br class=""></div><div class="">When I start the ChronoChat client, it creates certain default entries into the RIB as follows. </div><div class=""><br class=""></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class=""><div class="">/ndn/broadcast/chronochat/chatroom-list route={faceid=294 (origin=0 cost=0 ChildInherit)}</div></div><div class=""><div class="">/ndn/broadcast/ChronoChat/chatroom-e8745dec route={faceid=294 (origin=0 cost=0 ChildInherit)}</div></div><div class=""><div class="">/ndn/broadcast/%F0./chronochat-tmp-identity/f4e4ea96/CHRONOCHAT-INVITATION route={faceid=294 (origin=0 cost=0 ChildInherit)}</div></div></blockquote><div class=""><br class=""></div><div class="">I checked the faceId 294, and it is a non udp/tcp type of face. </div><div class=""><br class=""></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class="">faceid=294 remote=<a href="fd://23" class="">fd://23</a> local=<a href="unix:///run/nfd.sock" class="">unix:///run/nfd.sock</a> counters={in={70i 6d 16223B} out={0i 6d 5145B}} local on-demand point-to-point</div><div class=""><br class=""></div></blockquote>In what way I can program the ChronoChat client to use the specific face? may be through some configuration file or so? <div class=""><br class=""></div><div class="">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?</div><div class=""><br class=""></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px" class=""><div class="">faceid=257 remote=udp4://<a href="http://224.0.23.170:56363/" target="_blank" class="">224.0.23.170:56363</a> local=udp4://<a href="http://133.164.60.154:56363/" target="_blank" class="">133.164.60.154:56363</a> counters={in={0i 0d 0B} out={0i 0d 0B}} non-local persistent point-to-point</div></blockquote><span class="HOEnZb"><font color="#888888" class=""><div class=""><br class=""></div><div class="">/anil.</div><div class=""><br class=""></div></font></span></div>
</blockquote></div><br class=""></div>
_______________________________________________<br class="">Ndn-interest mailing list<br class=""><a href="mailto:Ndn-interest@lists.cs.ucla.edu" class="">Ndn-interest@lists.cs.ucla.edu</a><br class="">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest<br class=""></div></blockquote></div><br class=""></body></html>