12-08-2014 04:23 AM
With Hashing I can understand that a user is placed in the same vklan based on the Hash, so disconnecting and reconnecting you will have the same hash and be placed into the same VLAn.
This however leads to one VLAN being utilised more than another.
How does EVEN do it? When a user connects the 1st time and is placed in VLAN X - if the client disconnects and reconnects (for egsamople the user leaves the wifi coverage area for a short period of time) will the user remain in VLAN X when reconnecting or is there a possibility that he might be assigned to VLAN Y or Z?
Solved! Go to Solution.
12-08-2014 04:34 AM - edited 12-08-2014 04:44 AM
caveat 1: you must enable Preserve Client VLAN under vap profile to prevent exactly this issue on subsequent reconnect.
caveat 2: Preserve Client VLAN doesnt work across controllers, hence if you have any chance to roam between master/local or local/local, then even balance is not suitable for you.
the broadcast filtering in the controller is now at a point where pools of smaller (/24, /23) are not really required, a lot of larger campuses are up at the /18 size subnets, some even push it to /16
12-08-2014 04:47 AM
Lucky for me the roaming doesn't take place between controllers - so the single tick box, "Preserve Client VLA" is perfect THX - that makes it very simple from my side.
The client is trying to avoid supernets - at most they will go for a /23, but nothing bigger.