[Nfd-dev] nfdc route add issue with Ethernet Multicast

[Thiago Teixeira]

Thanks for the quick reply.

`nfdc route add /ndn 257` worked,
`nfdc route add /ndn ether://[01:00:5e:00:17:aa] local dev://eth1` did not.




From: susmit.shannigrahi at gmail.com [mailto:susmit.shannigrahi at gmail.com] On Behalf Of Susmit
Sent: Thursday, August 17, 2017 6:30 PM
To: Thiago Teixeira <tteixeira at engin.umass.edu>
Cc: <nfd-dev at lists.cs.ucla.edu> <nfd-dev at lists.cs.ucla.edu>
Subject: Re: [Nfd-dev] nfdc route add issue with Ethernet Multicast


Can you try this?
nfdc route add /ndn ether://[01:00:5e:00:17:aa] local dev://eth1



On Aug 17, 2017 4:21 PM, "Thiago Teixeira" <tteixeira at engin.umass.edu<mailto:tteixeira at engin.umass.edu>> wrote:
Hi all,

I have NFD and ndn-cxx 5.1 installed on a few GENI machines. They are fresh Ubuntu 16.04.1 LTS machines. I want to configure NDN over Ethernet multicast, but encountered issues.

Here’s my `nfdc face list` showing the two Ethernet faces (256 and 257) that were automatically created.
faceid=1 remote=internal:// local=internal:// counters={in={0i 60d 0n 38130B} out={116i 0d 0n 8956B}} flags={local permanent point-to-point local-fields}
faceid=254 remote=contentstore:// local=contentstore:// counters={in={0i 0d 0n 0B} out={0i 0d 0n 0B}} flags={local permanent point-to-point}
faceid=255 remote=null:// local=null:// counters={in={0i 0d 0n 0B} out={0i 0d 0n 0B}} flags={local permanent point-to-point}
faceid=256 remote=ether://[01:00:5e:00:17:aa] local=dev://eth0 counters={in={0i 0d 0n 0B} out={0i 0d 0n 0B}} flags={non-local permanent multi-access}
faceid=257 remote=ether://[01:00:5e:00:17:aa] local=dev://eth1 counters={in={0i 0d 0n 0B} out={0i 0d 0n 0B}} flags={non-local permanent multi-access}
faceid=258 remote=fd://29 local=unix:///run/nfd.sock counters={in={105i 3d 0n 7303B} out={3i 45d 0n 27457B}} flags={local on-demand point-to-point local-fields}
faceid=259 remote=udp4://224.0.23.170:56363<http://224.0.23.170:56363> local=udp4://172.17.1.5:56363<http://172.17.1.5:56363> counters={in={0i 0d 0n 0B} out={0i 0d 0n 0B}} flags={non-local permanent multi-access}
faceid=260 remote=udp4://224.0.23.170:56363<http://224.0.23.170:56363> local=udp4://10.10.4.2:56363<http://10.10.4.2:56363> counters={in={0i 0d 0n 0B} out={0i 0d 0n 0B}} flags={non-local permanent multi-access}
faceid=274 remote=fd://34 local=unix:///run/nfd.sock counters={in={1i 0d 0n 46B} out={0i 0d 0n 0B}} flags={local on-demand point-to-point}

And here’s my `nfdc route list`
1503006545.761235 INFO: [UnixStreamTransport] [id=0,local=unix:///run/nfd.sock,remote=fd://34] Creating transport
1503006545.761277 INFO: [FaceTable] Added face id=275 remote=fd://34 local=unix:///run/nfd.sock
prefix=/localhost/nfd nexthop=258 origin=app cost=0 flags=child-inherit expires=never
1503006545.771151 INFO: [Transport] [id=275,local=unix:///run/nfd.sock,remote=fd://34] setState UP -> CLOSING
1503006545.771459 INFO: [Transport] [id=275,local=unix:///run/nfd.sock,remote=fd://34] setState CLOSING -> CLOSED

I tried to add a face using the command `nfdc route add /ndn ether://[01:00:5e:00:17:aa]`, but since I have two Ethernet faces it threw an error:
Multiple faces match specified remote FaceUri. Re-run the command with a FaceId: 256 (local=dev://eth0), 257 (local=dev://eth1)

I re-ran the command appending the network device according to the above message:
`nfdc route add /ndn ether://[01:00:5e:00:17:aa] local=dev://eth1`

But got the error:
cannot parse 'local' as an argument name

Also tried just the network device, as described here<https://redmine.named-data.net/projects/nfd/wiki/FaceMgmt#Ethernet>, but got the same message.

What’s the correct syntax?

Thank you,
Thiago Teixeira


_______________________________________________
Nfd-dev mailing list
Nfd-dev at lists.cs.ucla.edu<mailto: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/20170817/d2d5e79a/attachment-0001.html>