Project

General

Profile

Task #4952

Minindn nodes have no their separated namespaces

Added by Jian Li over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Start date:
06/07/2019
Due date:
% Done:

0%

Estimated time:

Description

In mininet, there is a parameter --innamespace which is used to set an independent namespace for every switch. So that the environment variables set in different switches will not affect others. However, there is no parameter like this in minindn, If set one node the hostname as 'server', all of the nodes have the same hostname as 'server'.
In addition, the Minindn nodes have no their own home folder and environment variables. when we want to use the commonder like 'nfdc', we have to set the environment variables to the /tmp/minindn/.... firstly.

#1

Updated by Ashlesh Gawande over 1 year ago

Can you elaborate more on both the points, not sure I fully understand. I can review pull request on Mini-NDN if you have fixes ready or you can share the fixes here to help elaborate the problem.

#2

Updated by Jian Li over 1 year ago

Sorry, Maybe I should report this issue on Bug section, not this Task section. Both issues are about the miniNDN simulator
For the first issue, I think the miniNDN simulator has no parameter like the parameter '--innamespace' in the mininet simulator. The information about this parameter is described here: http://mininet.org/walkthrough/#everything-in-its-own-namespace-user-switch-only .
A separated namespace for each node is useful and necessary when we do some miniNDN experiments.

For the second issue, it is almost the same as Bug #3038 described. But it still exists. For example, when we start the minindn and turn on an Xterm node, we cannot use the commands like 'nfdc, nlsrc'. we have to set 'export HOME=/tmp/minindn/a' for every node, then we can use these commands.

Also available in: Atom PDF