07-20-2020 05:36 AM - edited 07-05-2021 12:18 PM
I have a Wireles LAN controller and Light weight access points broadcasting 2 SSIDs (Students-wifi and staff-wifi)on 2 differenet vlans(on packet tracer). Now the problem is the two APs are broadcasting the SSIDs to my wireless clients and i am now getting 4 SSIDs instead of just 2. I am getting Students- wifi, Students-wifi, Staff-wifi,Staff-wifi. If i add another AP, the number of SSIDS increases. How do i make my wireless clients to just receive 2 ssids and is there a way to make a clien device to always connect to a certain AP?
07-20-2020 05:43 AM - edited 07-20-2020 05:47 AM
That msut be the issue with packet tracer.
Normally AP will only broadcast WLANs what you create on WLC.
is there a way to make a clien device to always connect to a certain AP? yes or no .The decision to join which AP is the sole responsibility of the wireless NIC card of the client. You can help "influence" this by improving some of the settings on the WLC(ex: power level , disable low data rates...)
Regards
Dont forget to rate helpful posts
07-20-2020 08:05 AM
07-20-2020 09:34 AM
I would expect that everything is working perfectly fine here and the "problem" is caused by a misinterpretation of the view of the WLAN. So the first question is where are you seeing the SSIDs? Is it in the wireless neighbourhood of your PC or in a Wireless scanner?
On your PC you should see two SSIDs, but in a wireless scanner you see that both SSIDs are broadcasted by all APs. That is the way wireless works. The client should be able to connect to any AP whichever can serve the client best. For this, the client needs to see the SSIDs broadcasted from all APs.
The second question can also be answered when you know this behaviour. You typically do not want the client to only connect to one particular AP. Let the client decide which AP is the best to connect to.
07-23-2020 04:00 PM - edited 07-23-2020 04:11 PM
Scott and Karsten - I think you missed the fact that this is not a real network - it is on packet tracer which is a network emulation tool used for Cisco training. This is purely and simply a software bug in the software you're using amukoka and does not reflect real-life behaviour accurately.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide