When only VLAN mobility is enabled, does the client need to redo captive portal authentication after it roams to another controller?
Product and Software: This article applies to all Aruba controllers and ArubaOS versions.
When only VLAN mobility is enabled and mobile IP is disabled, there is no user authentication information communication between controllers except for the client's VLAN information via datapath bridge table synchronization.
When a client roams from one controller to another, its VLAN is not changed because VLAN mobility is enabled.
However, it has to redo the Layer 3 authentication if it is configured, that is, captive portal authentication.