[Nfd-dev] Ethernet multicast over multiple wireless hops

[Junxiao Shi]

Hi Thiago

NFD forwarding as of v0.5.0 is not designed for wireless networks.

Whether an Interest will be forwarded out of the same face as it came in is
up to the strategy, as nothing in forwarding pipelines prevents such
forwarding.
For BestRouteStrategy2, delete these lines
https://github.com/named-data/NFD/blob/037f4ab4b62f42447c78d25ede0755f98409c9cb/daemon/fw/best-route-strategy2.cpp#L71-L73
enables such forwarding.

Incoming Data pipeline will not forward a Data out of the same face as it
came in. This can be changed by deleting these lines
https://github.com/named-data/NFD/blob/037f4ab4b62f42447c78d25ede0755f98409c9cb/daemon/fw/forwarder.cpp#L365-L367

I do not know the implication on loop detection and PIT aggregation after
those changes are made. I'm CCing Teng Liang who recently implemented a
broadcast-based forwarding strategy for sensor networks where each node has
only one wireless NIC, as he may have a better idea on the implication.

Yours, Junxiao

On Wed, Dec 21, 2016 at 3:14 PM, Thiago Teixeira <tteixeira at engin.umass.edu>
wrote:

> 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*.
>
>
> 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?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20161221/7e6d7f51/attachment.html>