[Nfd-dev] Autoconfig for local WiFi network
shijunxiao at email.arizona.edu
Thu Mar 24 20:27:10 PDT 2016
I don’t understand why NdnCon instances can “magically” discover each other.
A standard NFD installation should create a multi-access Ethernet face on every multicast-capable network interface. However, it will not register any prefix onto these Ethernet faces, so these faces will not be used for communication.
Does your setup have another program that registers a prefix onto the Ethernet faces?
From NFD point of view, there’s no difference between wired Ethernet and WiFi, because Ethernet runs over WiFi.
However, some access points will block multicast traffic transmitted by a wireless stations, or even block all traffic between wireless stations.
You’ll need to configure your access point to permit multicast traffic among wireless stations.
> On Mar 24, 2016, at 6:37 PM, Gusev, Peter <peter at remap.ucla.edu> wrote:
> Hi dev team,
> Once we tested NDN over Ethernet on our local “testbed” - three laptops with NFD connected to the same network - after creating ethernet faces, ndncon instances running on each machine “magically” discovered each other and were able to communicate via chat/audio/video.
> However, I’m curious about feasibility of getting similar effect on the local WiFi networks (and whether autoconfig can help with that or such discovery should become a part of autoconfig):
> Say, I have three laptops with NFD connected to the same WiFi network with no Internet access. If I run autoconfig on all three laptops - will they “magically” discover each other and create routes? If so, which routes will be created?
> If no, what precludes from implementing such “local autodiscovery"?
> Peter Gusev
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nfd-dev