Roaming with WAP 351
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2016 07:56 AM - edited 07-05-2021 05:59 AM
Hello,
I'm currently doing an internship and i've been asked to set up a network with a radius server and two WAP 351 up to date.
As you will see in the attachment, the network is very simple.
Firstly, I have set up all the radius part with one WAP 351 and it worked well. I was able to use AD credentials to log on the network through the WAP with many devices like Iphone, Android and Windows computers.
Then I wanted my users to be able to roam in the room, so i added the second WAP. I made a cluster. Each WAP had:
- The same SSID
- The same authentication method (WAP2 ENTERPRISE)
- Different Channels
In this configuration, Roaming was successfully achieved when i used either an Iphone or an Android device. I could authenticate and walk from one side to another side of the room without losing connection. Downloads weren't interrupted and i could make a skype call without noticeable connection drop.
However, if i do the same with a windows computer, when the signal becomes too weak the computer do choose the second WAP but there is no network access. I know that roaming is a client based decision and the computer use the second WAP ( i see it because the WI-FI signal increase instantly) but i can't do anything. I need to restart the association. This behaviour has been seen with differents computers.
Did i miss something in the WAP configuration ?
Do i need WDS bridging to make it work with computers ?
EDIT : So, I launched Wireshark and found out that right after the handover the device send a lot of ARP requests which are not answered as you will see in the pictures below:
The selected frame in blue corresponds to the handover.
WINDOWS CLIENT IP: 172.19.20.6
Meraki IP: 172.19.20.1
After that, I set a static entry in the ARP table of the windows device which associate the meraki's MAC address and its IP address and it worked. The device could roam between the AP perfectly.
I would like to handle a lot of devices and adding ARP entries in each is not a option.
Do you know what is happening?
Is it possible that the ARP replies are sent to the AP that in first associated the device and not to the "New"?
Is there any configuration steps that I missed? (I don't think because iOS and Android device work fine)
Best regards,
Xavier
- Labels:
-
Aironet Access Points
