[Mini-NDN] Multi Router NLSR config

[S Khorasani]

Hi everyone,

Regarding my previous email on the output of running sudo minindn, I look
up for the reason. It seems that the problem occurs whenever mininet tries
to add links between nodes. As I'm using mini-NDN on vmware, may there be
any problem with vmware networking or any other settings? The output of
sudo minindn is as below:
Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
*** Creating network
*** Adding controller
*** Adding hosts:
a b c d
*** Adding switches:*** Adding links:
*** gave up after 3 retries

Regards

On Tue, Apr 12, 2016 at 1:14 AM, S Khorasani <s.kh.khorasani at gmail.com>
wrote:

> Dear Vince,
>
> The output of running sudo minindn is:
> Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
> *** Creating network
> *** Adding controller
> *** Adding hosts:
> a b c d
> *** Adding switches:
>
> *** Adding links:
> *** gave up after 3 retries
>
> I do not pass any file as parameter for manual execution of NLSR. So it
> uses the configuration file in the current directory. I run it in two
> directories and the results are as follow:
>
> - directory: /usr/local/etc/mini-ndn/
>
> Wrong configuration section: $GENERAL_SECTION
> Wrong configuration section: $NEIGHBORS_SECTION
> Wrong configuration section: $HYPERBOLIC_SECTION
> Wrong configuration section: $FIB_SECTION
> Wrong configuration section: $ADVERTISING_SECTION
> ERROR: error while connecting to the forwarder (No such file or directory)
>
> - directory: Source of NLSR from GitHub:
> Provided log directory </var/log/nlsr/> does not exist
> Error in configuration file processing! Exiting from NLSR
>
> Best Regards,
> skh
>
> On Tue, Apr 12, 2016 at 12:40 AM, Vince Lehman (vslehman) <
> vslehman at memphis.edu> wrote:
>
>> But mini-NDN fails (without any error message at CLI or log).
>>
>>
>> When you run “sudo minindn”, is there any output? If so, can you please
>> send the output?
>>
>> Also manual execution of NLSR results in bad config file's format.
>>
>>
>> Are you passing the configuration file as a parameter to NLSR (i.e., nlsr
>> -f /path/to/config/filename.conf) or do you have an NLSR configuration file
>> in the current directory when you run the “nlsr” command? If not, NLSR will
>> fail to parse the configuration, since it cannot find the configuration
>> file.
>>
>> --
>> Vince Lehman
>>
>> On Apr 11, 2016, at 3:00 PM, S Khorasani <s.kh.khorasani at gmail.com>
>> wrote:
>>
>> Dear Vince,
>>
>> My concern is that I have installed the source files on a new machine,
>> not the one that I already installed binary versions from PPA on it. So I
>> think that the problem is elsewhere. Could you please let me know other
>> probable sources of the problem?
>>
>> Regards,
>> skh
>>
>> On Mon, Apr 11, 2016 at 8:12 PM, Vince Lehman (vslehman) <
>> vslehman at memphis.edu> wrote:
>>
>>> Yes, the PPAs will either need to be removed or you will need to be sure
>>> that the binaries compiled and installed from source are the ones used by
>>> the system.
>>>
>>> The problem you are experiencing is due to the PPA version of NLSR
>>> expecting a configuration file at /etc/ndn/nlsr/nlsr.conf by default. The
>>> version installed from source expects nlsr.conf to be in the current
>>> working directory by default. When Mini-NDN runs NLSR, it does not
>>> explicitly specify a configuration file, so if you use the PPA version,
>>> each node will try to use the configuration in /etc/ndn/nlsr/nlsr.conf
>>> instead of the current working directory (which is each node’s home folder).
>>>
>>> This issue between source and PPA installs should be resolved when the
>>> task in http://redmine.named-data.net/issues/3039 is completed.
>>>
>>> --
>>> Vince Lehman
>>>
>>> On Apr 11, 2016, at 10:26 AM, Lan Wang (lanwang) <lanwang at memphis.edu>
>>> wrote:
>>>
>>> Maybe you need to clean up your previous PPA installation and then try
>>> the source installation.  Vince has seen similar problems before.
>>>
>>> Lan
>>>
>>> On Apr 10, 2016, at 2:26 PM, S Khorasani <s.kh.khorasani at gmail.com>
>>> wrote:
>>>
>>> Dear Ashlesh,
>>>
>>> In advance, thank you very much for your helps.
>>> Regarding your previous comment, I built and installed all packages from
>>> the sources regarding the instructions. The required paths created and
>>> files carefully copied to the paths.
>>> But mini-NDN fails (without any error message at CLI or log). Also
>>> manual execution of NLSR results in bad config file's format. Could you
>>> please let me know whether the problem is with defualt config file or
>>> mini-NDN executes NLSR with different config file. Where do you think the
>>> problem may be from?
>>>
>>> Many thanks,
>>> skh
>>>
>>> On Fri, Apr 8, 2016 at 1:24 AM, Ashlesh Gawande (agawande) <
>>> agawande at memphis.edu> wrote:
>>>
>>>> Mini-NDN does not support the PPAs yet. You will have to install
>>>> ndn-cxx, NFD, NLSR from source (make sure to uninstall the binaries first!).
>>>>
>>>> But you might be able to get it running:
>>>> Mini-NDN reads nlsr.conf and client.conf from /usr/local/etc/mini-ndn
>>>> which it copies over during installation.
>>>> nfd.conf should also be in this folder - copied from
>>>> /usr/local/etc/ndn/nfd.conf.sample
>>>>
>>>> Ashlesh
>>>> ------------------------------
>>>> *From:* S Khorasani <s.kh.khorasani at gmail.com>
>>>> *Sent:* Thursday, April 7, 2016 3:41 PM
>>>>
>>>> *To:* Ashlesh Gawande (agawande)
>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>> *Subject:* Re: [Mini-NDN] Multi Router NLSR config
>>>>
>>>> I installed binary version of NFD from
>>>> https://launchpad.net/~named-data/+archive/ppa (including ndn-cxx as
>>>> its prerequisite) and binary version of nlsr too. Then, I installed
>>>> mini-NDN from the source (available on GitHub) according to INSTALL.md.
>>>> However, when I run nlsr manually, it fails with the following error:
>>>> Failed to read configuration file: nlsr.conf
>>>> Error in configuration file processing! Exiting from NLSR.
>>>>
>>>>
>>>> On Fri, Apr 8, 2016 at 12:38 AM, Ashlesh Gawande (agawande) <
>>>> agawande at memphis.edu> wrote:
>>>>
>>>>> Can you please tell how you installed ndn-cxx, NFD, NLSR, and Mini-NDN?
>>>>>
>>>>> I would suggest first at least try to run with auto generated files
>>>>> before moving to manually configured files.
>>>>>
>>>>> Ashlesh
>>>>> ------------------------------
>>>>> *From:* S Khorasani <s.kh.khorasani at gmail.com>
>>>>> *Sent:* Thursday, April 7, 2016 3:05 PM
>>>>>
>>>>> *To:* Ashlesh Gawande (agawande)
>>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>>> *Subject:* Re: [Mini-NDN] Multi Router NLSR config
>>>>>
>>>>>
>>>>> Dear Ashlesh,
>>>>>
>>>>> Thank you very much for the response.
>>>>> I already checked the path, but there was no such
>>>>> directory(/etc/ndn/nlsr). So I added the directory and copied the file from
>>>>> the ndn_utils directory of the source and then run Mini-NDN. But the
>>>>> problem did not solve.
>>>>> Could you please let me know about the auto-generation mechanism of
>>>>> nlsr config file? Can I generate the config files of the nodes
>>>>> manually(using any script etc) and copy them to the nodes folders?
>>>>>
>>>>> Bests
>>>>>
>>>>>
>>>>> On Thu, Apr 7, 2016 at 11:35 PM, Ashlesh Gawande (agawande) <
>>>>> agawande at memphis.edu> wrote:
>>>>>
>>>>>> Can you check if there is a file at /etc/ndn/nlsr/nlsr.conf and at
>>>>>> ndn_utils/nlsr.conf?
>>>>>>
>>>>>> Ashlesh
>>>>>> ------------------------------
>>>>>> *From:* S Khorasani <s.kh.khorasani at gmail.com>
>>>>>> *Sent:* Thursday, April 7, 2016 11:55 AM
>>>>>> *To:* Ashlesh Gawande (agawande)
>>>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>>>> *Subject:* Re: [Mini-NDN] Multi Router NLSR config
>>>>>>
>>>>>> Dear Ashlesh,
>>>>>>
>>>>>> Thank you very much for your instant response. Unfortunately my setup
>>>>>> does not make any nlsr.conf file in nodes' home folder. I check the nlsr
>>>>>> log file and there, I find out that the problem is with parsing the
>>>>>> nlsr.conf file you addressed. The error message is:
>>>>>> "Failed to read configuration file: /etc/ndn/nlsr/nlsr.conf. Error
>>>>>> in configuration file processing! Exiting from NLSR"
>>>>>> So I confused what may be the problem now. Your further helps would
>>>>>> be appreciated.
>>>>>>
>>>>>> Sincerely,
>>>>>> skh
>>>>>>
>>>>>> On Wed, Apr 6, 2016 at 6:59 PM, Ashlesh Gawande (agawande) <
>>>>>> agawande at memphis.edu> wrote:
>>>>>>
>>>>>>> Mini-NDN generates the NLSR configuration files for you.
>>>>>>>
>>>>>>> You can check under /tmp/<node-name>/nlsr.conf
>>>>>>>
>>>>>>> Mini-NDN copies this file
>>>>>>> https://github.com/named-data/mini-ndn/blob/master/ndn_utils/nlsr.conf
>>>>>>> after filling in appropriate sections to each node's home folder
>>>>>>> /tmp/<node-name>/
>>>>>>>
>>>>>>> Does this answer your question?
>>>>>>>
>>>>>>> Ashlesh
>>>>>>> ------------------------------
>>>>>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>>>>>>> S Khorasani <s.kh.khorasani at gmail.com>
>>>>>>> *Sent:* Wednesday, April 6, 2016 3:32 AM
>>>>>>> *To:* mini-ndn at lists.cs.ucla.edu
>>>>>>> *Subject:* [Mini-NDN] Multi Router NLSR config
>>>>>>>
>>>>>>> Salaam,
>>>>>>>
>>>>>>> I'm beginner in using mini-NDN emulator and have  encountered
>>>>>>> problem in configuration of NLSR. My problem is exactly with multi router
>>>>>>> configuration. In fact I do not know how can I prepare a nlsr.conf file
>>>>>>> that could be matched with default topology of mini-NDN
>>>>>>> (default-topology.conf file). As I find out, the default topology is for a
>>>>>>> multi router scenario (4 nodes), but the default configuration file of NLSR
>>>>>>> (nlsr.conf|) is not compatible with this scenario.
>>>>>>> So it would be my pleasure if everyone could help me.
>>>>>>>
>>>>>>> Kind Regards,
>>>>>>> skh
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>> _______________________________________________
>>> Mini-NDN mailing list
>>> Mini-NDN at lists.cs.ucla.edu
>>> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>>>
>>>
>>> _______________________________________________
>>> Mini-NDN mailing list
>>> Mini-NDN at lists.cs.ucla.edu
>>> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>>>
>>>
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160415/2183628d/attachment.html>