[Nfd-dev] Autoconfig for local WiFi network
jburke at remap.UCLA.edu
Fri Mar 25 09:19:19 PDT 2016
"You’ll need to configure your access point to permit multicast traffic among wireless stations."
I mentioned to Peter that I thought this was the case. I think the concern here is that in "real life", where Peter is hoping to experiment with NDN-RTC more and more, we can't always control infrastructure in this way.
So what Peter is asking is whether there is (or could be) a way to automatically bootstrap local communication between NFDs on different devices connected to the same not-necessarily-internet-connected access point without requiring any configuration on the AP.
(Peter please correct me if I'm wrong)
From: Nfd-dev <nfd-dev-bounces at lists.cs.ucla.edu<mailto:nfd-dev-bounces at lists.cs.ucla.edu>> on behalf of "Gusev, Peter" <peter at remap.UCLA.edu<mailto:peter at remap.UCLA.edu>>
Date: Thursday, March 24, 2016 at 8:57 PM
To: Junxiao Shi <shijunxiao at email.arizona.edu<mailto:shijunxiao at email.arizona.edu>>
Cc: "<nfd-dev at lists.cs.ucla.edu<mailto:nfd-dev at lists.cs.ucla.edu>>" <nfd-dev at lists.cs.ucla.edu<mailto:nfd-dev at lists.cs.ucla.edu>>
Subject: Re: [Nfd-dev] Autoconfig for local WiFi network
My bad, I forgot mentioning that we registered a prefix (it was something simple as “nfdc register / <face-id>”).
peter at remap.ucla.edu<mailto:peter at remap.ucla.edu>
+1 213 5872748
Software Engineer/Programmer Analyst @ REMAP UCLA
Video streaming/ICN networks/Creative Development
On Mar 24, 2016, at 8:27 PM, Junxiao Shi <shijunxiao at email.arizona.edu<mailto:shijunxiao at email.arizona.edu>> wrote:
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<mailto: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"?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nfd-dev