[Ndn-interest] How to use NDN on real devices?

[Otávio Augusto]

Hi Lan. First, thanks for the reply.

My focus is not on routing and my network must be relatively small, so I
believe it is more interesting, at least in the beginning, to manually
write the forwarding strategies.

I am sending an attached image that contains the topology that I might use,
where PC*x* are network devices; User1 is a user (consumer); R*x* are
routers; solid lines are ethernet communication and dotted lines are WiFi
communications.

Here are some points I need to confirm:

1- Should the routers also be computers with the libraries installed
(ndn-cxx and NFD, without NLSR)?

2- To add the faces to the devices, would it be necessary to run the *"nfdc
face create"* command on each device, according to the defined connections
and the available content?

3- Apparently, the "UDP/TCP faces" use the device's IP as a kind of
identifier (like: udp4://192.0.2.1:6363). So, all devices need to have an
IP (preferably static)? Also, do the devices need to be on the same IP
network?

Thanks,
Otavio da Cruz

Em sáb., 6 de mai. de 2023 às 17:24, Lan Wang (lanwang) <lanwang at memphis.edu>
escreveu:

> Hi Otávio,
>
> NLSR works only on point-to-point links right now.  You can set up UDP
> tunnels over Wifi links if you want to run NLSR for routing.
> Alternatively, if you have a small and fixed network topology, you can use
> nfdc commands to set up the routes in each node manually.  You can run NDN
> on Ethernet/WiFii faces and Interests will reach the other nodes sharing
> the Ethernet/WiFi.
>
> Lan
>
> On May 2, 2023, at 9:21 PM, Otávio Augusto via Ndn-interest <
> ndn-interest at lists.cs.ucla.edu> wrote:
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and trust
> the content is safe.
> Hello everybody.
> I've been working on a project that uses NDN. We are planning a practical
> demonstration and would like to know what are the possible strategies I
> have available to do this. That is, "common devices" (like personal
> computers) are generally based on TCP/IP, not NDN.
>
> If I understand correctly, I just need to install ndn-cxx, NFD (Named Data
> Networking Forwarding Daemon) and NLSR (Named Data Link State Routing) on
> the computer and I can already communicate using NDN. But I didn't
> understand exactly how. Would it be a kind of NDN over TCP/IP? Or
> tunneling? Or would it be "purely NDN" communication?
>
> Also, if I install these components (ndn-cxx, NFD and NLSR), can I
> communicate over a wireless network? For example, 5 notebooks communicating
> via wi-fi. I ask this because it seems to me that support is for networks
> connected via cable (ethernet, perhaps).
>
> Another point, can I communicate between the devices via the internet?
> How? Do you have an example available?
>
> Also, I would like to know the possible workload to implement NDN in a
> topology with about 5 devices, maybe with a few routers.
>
> The experience I have (even if very little) is with the mini-NDN. I'm
> currently trying to set the demonstrator over there.
>
> Sorry for so many questions. Thank you very much in advance.
>
> Att, Otávio A. R. da Cruz
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> https://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20230507/7a4fc4b0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diagram.png
Type: image/png
Size: 43646 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20230507/7a4fc4b0/attachment-0001.png>