Open Yunmei-Xiao opened 9 years ago
Hi Yunmei,
currently there is no configuration-based end host mobility support, it is actually one of the topics on our roadmap but with no prevision to be completed in the near term. The dynamic changing of the topology mentioned in the quote above refers to the ability of bringing interfaces up and down via Linux ifconfig commands.
One suggestion I would have in case you want to try a quick and dirty end-host mobility scenario would be defining an end-host with multiple interfaces and attaching each of one to the switches along the "path" the end host would be moving, ie.would have one interface attached to. Then I would bring down all interfaces except one, and you could try "simulating" the mobility of the end host by bringing the interfaces up and down as the end host "moves".
Let us know how it goes.
Cheers, Christian
Christian
On Fri, Sep 26, 2014 at 10:39 AM, Yunmei-Xiao notifications@github.com wrote:
I plan to emulate a scenario where the end hosts move from one switch to another.
I read the tutorials on Mini-CCNx github webiste, and wrote a configuration file to create about 40 NDN nodes. The ccnping command worked fine. So I think I have understood the basic grammar of the configuration file.
But how could I implement the mobility of end hosts by configuration file? Is it possible to use Mini-CCNx to emulate the scenario where the end hosts move around?
The github miniccnx website mentions that “you can dynamically interact with the topology, bring the links down, and check how the routing algorithm converges!”, Where can I get more details of dynamically changing the topology?
Looking forward to your replay! Thanks!
Best regards.
Yunmei Xiao
— Reply to this email directly or view it on GitHub https://github.com/chesteve/mn-ccnx/issues/8.
Thanks Christian! I tried your suggestion and now have a new issue.
I write a Perl script to perform the "ifconfig ethN up/down" commands. When I type the command "perl xxx.pl" in the terminal, the script runs correctly. In my scenario there are hundreds of hosts, therefore I need the numerous virtual hosts run their individual script automatically, right after been created. It is not feasible if I have to open each xterm and type the "perl xxx.pl" command.
My question is, how could I make the created hosts run the script automatically, and keep running? Do I need to change the Perl script into another form of executable file?
I know that the configuration script "miniccnx.conf" allows to specify one or more applications. I tried to use "./xxx.pl" in the position of app (already chmod +x xxx.pl). The script didn't work, or maybe it ran and finished, but I need to have the script/application started and kept running. If I write "while(1)" loop in the script, miniccnx won't create normally.
Looking forward to your help! Thanks!
Best regards,
Yunmei Xiao
Hi Xiao,
I would like to help you at this point but I have no clue what may be going on. I suggest you post the question (along the code from your script .pl) to the mininet list where people may have faced similar issues with running automated scripts in the LXC containers.
Lets us know of any progress please!
Thanks, Christian
Christian
On Thu, Oct 30, 2014 at 1:27 AM, Yunmei-Xiao notifications@github.com wrote:
Thanks Christian! I tried your suggestion and now have a new issue.
I write a Perl script to perform the "ifconfig ethN up/down" commands. When I type the command "perl xxx.pl" in the terminal, the script runs correctly. In my scenario there are hundreds of hosts, therefore I need the numerous virtual hosts run their individual script automatically, right after been created. It is not feasible if I have to open each xterm and type the "perl xxx.pl" command.
My question is, how could I make the created hosts run the script automatically, and keep running? Do I need to change the Perl script into another form of executable file?
I know that the configuration script "miniccnx.conf" allows to specify one or more applications. I tried to use "./xxx.pl" in the position of app (already chmod +x xxx.pl). The script didn't work, or maybe it ran and finished, but I need to have the script/application started and kept running. If I write "while(1)" loop in the script, miniccnx won't create normally.
Looking forward to your help! Thanks!
Best regards,
Yunmei Xiao
— Reply to this email directly or view it on GitHub https://github.com/chesteve/mn-ccnx/issues/8#issuecomment-61041110.
Thanks Christian. I'll try your suggestion and update the progress.
Yunmei
xyunmei@gmail.com
From: Christian Esteve Rothenberg Date: 2014-11-01 21:17 To: chesteve/mn-ccnx CC: Yunmei-Xiao Subject: Re: [mn-ccnx] How to emulate end host mobility? (#8) Hi Xiao,
I would like to help you at this point but I have no clue what may be going on. I suggest you post the question (along the code from your script .pl) to the mininet list where people may have faced similar issues with running automated scripts in the LXC containers.
Lets us know of any progress please!
Thanks, Christian
Christian
On Thu, Oct 30, 2014 at 1:27 AM, Yunmei-Xiao notifications@github.com wrote:
Thanks Christian! I tried your suggestion and now have a new issue.
I write a Perl script to perform the "ifconfig ethN up/down" commands. When I type the command "perl xxx.pl" in the terminal, the script runs correctly. In my scenario there are hundreds of hosts, therefore I need the numerous virtual hosts run their individual script automatically, right after been created. It is not feasible if I have to open each xterm and type the "perl xxx.pl" command.
My question is, how could I make the created hosts run the script automatically, and keep running? Do I need to change the Perl script into another form of executable file?
I know that the configuration script "miniccnx.conf" allows to specify one or more applications. I tried to use "./xxx.pl" in the position of app (already chmod +x xxx.pl). The script didn't work, or maybe it ran and finished, but I need to have the script/application started and kept running. If I write "while(1)" loop in the script, miniccnx won't create normally.
Looking forward to your help! Thanks!
Best regards,
Yunmei Xiao
— Reply to this email directly or view it on GitHub https://github.com/chesteve/mn-ccnx/issues/8#issuecomment-61041110.
— Reply to this email directly or view it on GitHub.
I plan to emulate a scenario where the end hosts move from one switch to another.
I read the tutorials on Mini-CCNx github webiste, and wrote a configuration file to create about 40 NDN nodes. The ccnping command worked fine. So I think I have understood the basic grammar of the configuration file.
But how could I implement the mobility of end hosts by configuration file? Is it possible to use Mini-CCNx to emulate the scenario where the end hosts move around?
The github miniccnx website mentions that “you can dynamically interact with the topology, bring the links down, and check how the routing algorithm converges!”, Where can I get more details of dynamically changing the topology?
Looking forward to your replay! Thanks!
Best regards.
Yunmei Xiao