[Ndn-interest] Request for help with running ndnping and ndnpingserver on our testbed

[Lan Wang (lanwang)]

I’m not sure if L3 tunneling is the problem or not.  A few more suggestions:

- make sure nfd is running on node 2.
- make sure the application faces between nfd and ndnping are working on both node 1 and node 2.
- use tshark to capture the traffic traces on both nodes to see if the packets were sent by nfd on node 1 and received by nfd on node 2.

Lan

On Jan 15, 2024, at 11:26 AM, Navaneet Y V N . <navaneetyvn.211cs234 at nitk.edu.in> wrote:

Hi Lan,
Adding to my previous email, I would like to add a point.
L3 tunneling is blocked by our college routers and we would like to know if this could be a possible reason for our issue.

Thanks,
Navaneet

On Mon, Jan 15, 2024 at 10:52 PM Navaneet Y V N . <navaneetyvn.211cs234 at nitk.edu.in<mailto:navaneetyvn.211cs234 at nitk.edu.in>> wrote:
Hi Lan,
Thanks for writing to us. I have attached two screenshots with this email.
fib.png - output of nfdc fib list and nfdc face list
nfd-fib.png - output from the terminal where nfd is running.
node1 is my device running ndnping
You can find he id=261 in both the screenshots which shows the ip address of node 2 which is running ndnpingserver . node1 is the consumer requesting for /A data packets(ping) from node2 which is the producer running ndnpingserver. I hope this clarifies your query.

Thanks,
Navaneet

On Mon, Jan 15, 2024 at 10:11 PM Lan Wang (lanwang) <lanwang at memphis.edu<mailto:lanwang at memphis.edu>> wrote:
How do you know the routes are correctly set up?  Can you show a screenshot of the nfd FIB on node 1?

Lan

On Jan 13, 2024, at 11:40 AM, Navaneet Y V N . via Ndn-interest <ndn-interest at lists.cs.ucla.edu<mailto: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.

Dear Members of the community,

My team is working on setting up a testbed that runs on NDN. The testbed consists of 5 Raspberry Pi-4 devices all connected to an L2 switch(D-Link Switch DGS-1250-28X) via ethernet and this switch is connected to a private network. The R-Pi devices each run Ubuntu Server 22.04.03 LTS and all of them have NFD, ndn-cxx and ndn-tools installed along with their dependencies and the steps mentioned in the respective github repositories of NDN. I was able to successfully run the producer-consumer example on all our R-Pi devices.

When I decided to test out the connectivity of two R-Pi devices in this setup over NDN, I tried running ndnping server on one device and ndnping on the other which is not working. I followed the steps mentioned here<https://github.com/named-data/ndn-tools/tree/master/tools/ping> on the ndn-tools documentation on github. I have made sure to add the respective interfaces and routes (using nfdc face create and nfdc route add, while using udp4) and also made sure that NFD is running properly. We do not understand what is the issue here and we could really use some help.

I have attached the screenshots of the terminal from testing the ndnping and ndnpingserver commands. Please write to us if you need any more clarifications on our issue.

Thanks,
Navaneet
<Screenshot from 2024-01-13 20-19-33.png><Screenshot from 2024-01-13 20-21-32.png>_______________________________________________
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu<mailto: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/20240115/9bab2662/attachment-0001.html>