[Nfd-dev] Ethernet multicast over multiple wireless hops

[Thiago Teixeira]

Hi,

I have a topology of five wireless nodes all running NFD v.0.5. on Ubuntu 16.04. I am using Ethernet as the transport method with one multicast group, as follows face_system.ether. mcast_group 01:00:5E:00:17:AA.

I am using "nfdc register /ndn/broadcast ether://[01:00:5E:00:17:AA]" to register nodes to the multicast group, which creates the following faces:
Faces:
  faceid=1 remote=internal:// local=internal:// counters={in={0i 19d 0n 10752B} out={29i 0d 0n 2940B}} local permanent point-to-point flags={local-fields}
  faceid=254 remote=contentstore:// local=contentstore:// counters={in={0i 0d 0n 0B} out={0i 0d 0n 0B}} local permanent point-to-point flags={}
  faceid=255 remote=null:// local=null:// counters={in={0i 0d 0n 0B} out={0i 0d 0n 0B}} local permanent point-to-point flags={}
  faceid=256 remote=udp4://224.0.23.170:56363 local=udp4://10.0.0.9:56363 counters={in={0i 0d 0n 0B} out={0i 0d 0n 0B}} non-local permanent multi-access flags={}
  faceid=257 remote=ether://[01:00:5e:00:17:aa] local=dev://eth0 counters={in={0i 0d 0n 0B} out={0i 0d 0n 0B}} non-local permanent multi-access flags={}
  faceid=258 remote=fd://25 local=unix:///run/nfd.sock counters={in={18i 2d 0n 3297B} out={3i 10d 0n 6406B}} local on-demand point-to-point flags={local-fields}
  faceid=261 remote=fd://26 local=unix:///run/nfd.sock counters={in={6i 0d 0n 314B} out={0i 0d 0n 0B}} local on-demand point-to-point flags={}
FIB:
  /localhost/nfd/rib nexthops={faceid=258 (cost=0)}
  /ndn/broadcast nexthops={faceid=257 (cost=0)}
  /localhost/nfd nexthops={faceid=1 (cost=0)}
RIB:
  /ndn/broadcast route={faceid=257 (origin=255 cost=0 ChildInherit)}
  /localhost/nfd route={faceid=258 (origin=0 cost=0 ChildInherit)}

When I test connectivity using NDN-Ping it works between one hop neighbors, but not over multiple hops. I assume that is because the architecture prevents it from sending Int/Data packets over the same face it received, in order to prevent loops. Am I right?
If so, what is the best way to address this issue?

Thanks,
Thiago

PS: my issue is a bit different from this (http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2015-April/001018.html) because I have only one Ethernet interface.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20161221/bb34b6f2/attachment.html>