[Nfd-dev] NDN through NATs

[Alex Afanasyev]

How would you manage such a node?  If it is behind the NAT (without any
ports redirected, then it will only be able establish connectivity to the
testbed and there could be issues getting status (from web interface).

--
Alex


On Sun, Apr 9, 2017 at 3:12 PM, Dehart, John <jdd at wustl.edu> wrote:

>
> All:
>
> In our policy statement (https://named-data.net/ndn-
> testbed/policies-connecting-nodes-ndn-testbed/)
> for a site joining the NDN Testbed, we state:
>
> "The machine may be a dedicated physical box or a virtual machine (VM)
> with a
>   publicly routable IP address (i.e., should not be behind a NAT). “
>
> I would like to lift the restriction about being behind a NAT. I believe
> that we originally put
> that stipulation in the policy as a convenience to us as we managed the
> NDN Testbed.
> We have already been flexible with a couple of sites that wanted or needed
> to be behind a NAT.
> So far, I do not have any evidence that this has caused any problems. We
> do have an issue with
> one site that happens to be behind a NAT but at this time I do not think
> the NAT is causing the problem.
>
> Does anyone have any concrete reasons why an NDN node on the NDN Testbed
> should
> NOT be allowed to be behind a NAT?
>
> Thanks,
> John
>
>
> _______________________________________________
> 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/20170409/bca31999/attachment.html>