Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wifi-roaming.py #112

Open
dside99 opened this issue Jun 11, 2017 · 6 comments
Open

wifi-roaming.py #112

dside99 opened this issue Jun 11, 2017 · 6 comments

Comments

@dside99
Copy link

dside99 commented Jun 11, 2017

Hello,

Running wifi-roaming.py I realized that controller doesn't exist in the simulation. So, I uncommented the relative lines but the controller still doesn't exist in the simulation. Is there any solution?

Thank you.

@charlesmcchan
Copy link
Contributor

The controller is external to the simulation environment. You need to setup the controller separately. Any controller should work as long as they speak OpenFlow and is reachable from the physical machine you are running OpenNet.

@dside99
Copy link
Author

dside99 commented Jun 12, 2017

I understand that in this simulation there isn't any controller. So, the experiment using 7 APs and 2 hosts is not about sdn, isn't it? If yes, why the first ping is takes so many times longer than the second?
Is there any example to completelly understand what I have to do to add the controller in the simulation?

Thank you in advance!

@charlesmcchan
Copy link
Contributor

It is definitely SDN. However, the controller is not a simulated node running inside OpenNet. You need to prepare a real OpenFlow controller and connect your simulated switches to it.

Some controller, such as ONOS, can be run inside a Mininet environment. However, I don't think there is an existing example for doing this in OpenNet. You might need to develop your own.

@dside99
Copy link
Author

dside99 commented Jun 12, 2017

It's nice idea to contribute on your project. I saw this problem on all mininet examples running OpenNet. But let me ask you why it is SDN, because I think SDN requires a controller conected to Openflow switches to populate the the flow entries etc...

@kansokusha
Copy link
Contributor

Since we noticed that some users do not know how to launch SDN controller when they trying to run our example scripts, the fail mode of all emulated OpenFlow switches in the script are set to standalone. User can run these scripts with/without SDN controller.

For more detail about fail mode, please refer OpenFlow Switch Specification.

For users who want to use SDN controller in OpenNet script, they can start from reading Mininet tutorial, the approach of adding SDN controller in OpenNet script is the same as Mininet.

@dside99
Copy link
Author

dside99 commented Jun 12, 2017

Actually, I can't totally understand you. I realize that the OpenFlow switch turns into standalone mode in order to deal without controller. Sure, I have to study about fail mode and Mininet tutorial. I supposed that Mininet examples could be executed in OpenNet enviroment, but they failed due to controller absence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants