[Nfd-dev] Emergency

[Junxiao Shi]

Hi John

No it would not. It could only affect ARIZONA, because the prefix I use is
under /ndn/edu/arizona, and my "server" endpoint is connected only to
ARIZONA. The "client" endpoint would connect to a router in China (I intend
to use it as backup VPN when I'm back to China), but it's not running on
Monday.

Yours, Junxiao

On Aug 25, 2017 6:52 AM, "Dehart, John" <jdd at wustl.edu> wrote:


Junxiao,

Do you see anyway that when it was broken it would have affected almost all
of the NDN Testbed nodes?

John

On Aug 25, 2017, at 8:36 AM, Junxiao Shi <shijunxiao at email.arizona.edu>
wrote:

Hi John

The tunneling app is running at all time. It has been fixed: the remote
endpoint is offline, the consumer would keep only one outstanding Interest.

Yours, Junxiao

On Aug 25, 2017 6:25 AM, "Dehart, John" <jdd at wustl.edu> wrote:

Junxiao,

Would it be possible for you to run your tunnelling app again to see if it
causes NDN Testbed problems?
I am trying to recreate the problem we had on Monday.  So far, I haven’t
see it happen again.
I’ve tried a small set of my AWS instances and Haitao has tried his
namespace-tree experiment.
But so far neither has caused any problems.

Thanks,
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20170825/f3da0fda/attachment.html>