[Nfd-dev] Issues connecting to the testbed <BLOCKING>

Junxiao Shi shijunxiao at email.arizona.edu
Wed May 4 16:00:38 PDT 2016

Hi Spyros

End host 1 is possibly having some IP layer issues. Wireshark will be
helpful in finding out why the face is closed.

For end host 2, if you want /NTORRENT to show up on spurs's RIB, some
component on the end host must send a prefix registration command to spurs,
and the command must be signed by a testbed certificate.
NFD-RIB automatic prefix propagation won't send such a command. It would
send a prefix registration command for /NTORRENT only if there's a
/NTORRENT identity in NFD-RIB's key chain; but even if you have such an
identity, the certificate won't be a trusted testbed certificate.
Thus, you need another tool such as remote-register-prefix
to send this command periodically.
Alternatively, talk to your site's testbed operator to register a static
route, if end host 2 has a static IP.

Yours, Junxiao
On May 4, 2016 1:48 PM, "Spyridon (Spyros) Mastorakis" <
mastorakis at cs.ucla.edu> wrote:

> Hi,
> so, here is the story:
> We are trying to test nTorrent on the testbed (across the spurs node).
> We have 2 issues that seem to be preventing us from moving forward:
> 1) Consumer side (me) uses ‘nfdc register /NTORRENT
> tcp://spurs.cs.ucla.edu” this returns success but local NFD shows that
> the face is closed (and the connection was shut down) and no traffic (ping
> for example) is seen from the testbed.
> 2) The producer side (mickey) runs the same command, does not see the same
> failure messages from NFD. However, /NTORRENT does not show up on the spurs
> status page. He does however see ping traffic, etc from the testbed so
> there does seem to be a working tunnel.
> We have already verified that our certificates are correct, and have
> restarted NFD numerous times.
> We are currently blocked to make progress and would therefore greatly
> appreciate some prompt assistance.
> Thank you in advance,
> Spyridon (Spyros) Mastorakis
> Personal Website: http://cs.ucla.edu/~mastorakis/
> Internet Research Laboratory
> Computer Science Department
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160504/dc911967/attachment.html>

More information about the Nfd-dev mailing list