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

Handover in Mininet-wifi in a Mobility scenario with AP in same channel as well as different channel #13

Open
massvoice opened this issue Apr 9, 2019 · 1 comment

Comments

@massvoice
Copy link

massvoice commented Apr 9, 2019

Hi,

I am currently working on a Mobility scenario in Mininet-Wifi which requires handovers between APs of same channel as well as different channel.

I have tired using OdinMobilityManager Application and it works perfectly as stated in the same channel AP while I use MobilityManager Application for APs in different channel. .

Is there any way I can use either of the application to simulate my need. It will be of great help.

Thanks.

@josemariasaldana
Copy link
Member

As you can see here (https://github.com/Wi5/odin-wi5/wiki/Applications)
SmartApSelection: It is a proactive application that is in charge of mobility management and load balancing simultaneously. It performs periodical scans, gets the information and, if needed, hands off STAs between APs. It has different modes for load balancing.

MobilityManager: It is a reactive application that is in charge of handoffs. When the STA moves, the origin AP reports this fact to the controller, and this triggers the whole proccess. The statistics obtained with the auxiliary wireless interface are used for selecting the best suited AP for the STA. A seamless handoff is run between the "origin" and the "destination" APs. It is not coordinated with load balancing.

Both applications perform multi-channel handoffs when needed. BUT if the APs are in the same channel, they perform single-channel handoffs.

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

2 participants