@cjoseph wrote:
Not possible unless the client sees that the link goes down. You cannot roam between buildings on the same SSID and make the client change ip addresses, period.
This is not always true. Only with Windows laptops have we noticed this behavior. Other clients (e.g., iOS, Android, MacOS) will roam and perform 802.1X authentication, followed by sending a DHCPREQUEST for the IP the last had. DHCP servers should then respond with a DHCPNAK (assuming they're now on a different network), forcing the client to go ahead with a DHCPDISCOVER packet and obtain an address in the new network. We see this correct behavior all the time.
@cjoseph wrote:
Network administrators should design their networks so that users who roam maintain the same ip address for seamless performance. There is no advantage to changing ip addresses within the same network.
I agree - no advantage. However, with large geographic networks like ours, changing IP is inevitable. ArubaOS' vlan pooling hash algorithm deteriorates the more vlans you have in the pool, so I cannot maintain a single vlan pool across the campus. Thus, I must establish hard roaming boundaries wherein users will change their IP.