[Ndn-interest] Sending data over physical interface

[Lixia Zhang]

wonder if you can be more specific on the scenarios?
if it is small scale, you may as well use self-learning instead of NLSR.

regarding face ID: since I dont look the code I can be wrong, but that's not the routing issue but node config. I believe you need to config, others can tell you how

> On Feb 15, 2019, at 8:06 PM, Lee, Jongdeog via Ndn-interest <ndn-interest at lists.cs.ucla.edu> wrote:
> 
> Dear Prof. Lixia Zhang and Spyros,
> 
> Thanks for the reply.
> I think my example confused both of you. I need a routing protocol.
> 
> Let's have 4 nodes instead of 2. The following is the topology:
> 
> /A -- /B
>  |       |
> /C -- /D
> 
> When all 4 nodes run NLSR and they are physically connected as above, what extra steps should I take to send packets over the links?
> Does it automatically create a face ID (without nfdc command)? Or should I create it manually?
> Once the face is registered, the route is automatically added by NLSR, I guess?
> 
> Best wishes,
> Jongdeog Lee (JD)
> 
> ------------------------------------------------
> Ph.D. Student
> Department of Computer Science
> University of Illinois at Urbana-Champaign
> From: Spyridon (Spyros) Mastorakis <mastorakis at cs.ucla.edu <mailto:mastorakis at cs.ucla.edu>>
> Sent: Friday, February 15, 2019 9:04 PM
> To: Lee, Jongdeog
> Cc: ndn-interest
> Subject: Re: [Ndn-interest] Sending data over physical interface
>  
> JD,
> 
> if your topology is simple as you said (2 nodes), you can directly send packets from one node to the other.
> 
> NFD should have created ethernet faces and you use the nfdc command to establish a new route through the ethernet face directly (i.e., run NDN over L2). You do not need a routing protocol for such a simple scenario.
> 
> Hope this helps,
>  
> Spyridon (Spyros) Mastorakis
> Personal Website: http://cs.ucla.edu/~mastorakis/ <https://urldefense.proofpoint.com/v2/url?u=http-3A__cs.ucla.edu_-7Emastorakis_&d=DwMFAg&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=RTtNIB7SLbCEZbcCvc1ADsIJ3mCRR77CzZSVcwLWK6w&m=Us2dbX7dkEIc8oima_PFnw08HPpG55QvJJWN_1eRrsc&s=IGhq-iMYKg1hpvs_VdyZ3iRtWF6T5Jj3OuEw3Jm7nCk&e=>
> Internet Research Laboratory
> Computer Science Department
> UCLA
> 
>> On Feb 15, 2019, at 2:07 PM, Lee, Jongdeog via Ndn-interest <ndn-interest at lists.cs.ucla.edu <mailto:ndn-interest at lists.cs.ucla.edu>> wrote:
>> 
>> Hi all,
>> 
>>   Hope all of you are doing good.
>>   Sorry in advance if this question is duplicate.
>> 
>>   I would like to send NDN interest/data packets over physical interfaces, not TCP/UDP pipes.  
>>   Suppose that we have two directly connected nodes over the wireless medium.
>>   Both nodes have nfd, ndn-cxx, and nlsr (chronosync and psync accordingly) installed.
>> 
>>   If I run nlsr on both nodes, then do these forward NDN packets to each other without any extra configurations?
>>   Or should I create the face and add a route on each node using nfdc command?
>> 
>> Best wishes,
>> Jongdeog Lee (JD)
>> 
>> ------------------------------------------------
>> Ph.D. Student
>> Department of Computer Science
>> University of Illinois at Urbana-Champaign
>> _______________________________________________
>> Ndn-interest mailing list
>> Ndn-interest at lists.cs.ucla.edu <mailto:Ndn-interest at lists.cs.ucla.edu>
>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.lists.cs.ucla.edu_mailman_listinfo_ndn-2Dinterest&d=DwMFAg&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=RTtNIB7SLbCEZbcCvc1ADsIJ3mCRR77CzZSVcwLWK6w&m=Us2dbX7dkEIc8oima_PFnw08HPpG55QvJJWN_1eRrsc&s=iQQ5ongiTu0lX96ltjVwKULEmlvjWnXlsqyhYEXukD4&e=>
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu <mailto:Ndn-interest at lists.cs.ucla.edu>
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest <http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20190216/b71cfef4/attachment-0001.html>