Solved

Release note WING 5.9.5

  • 15 July 2019
  • 3 replies
  • 343 views

Userlevel 2
Hello guys,

There is some NEW FEATURE IN WING 5.9.5:


What does it mean in this case, it's about an upgrade to roaming procedure or just for debugging needs?

Thanks

Aviv
icon

Best answer by Chris Kelly 15 July 2019, 17:39

Aviv, it's not an update to the actual roaming algorithms or procedure. It's about what happens in regards to an AP initiating (not initiating) an accounting request (START) message and re-authenticating to the RADIUS accounting server, in a client roam event.

First, without this option, the accounting data is not migrated from the old AP to the new AP when a roam occurs. Only various bits of info are migrated, like the device's VLAN, it's IP address, etc. Also, an accounting STOP request is sent by the old AP to the accounting server and then an accounting START request is then sent by the new AP to the accounting server.

With this new option, a client's roam will then only continue to cause an accounting START request from the original AP and...here's the change... an accounting STOP request from the new AP *ONLY* when it roams away. This option prevents the additional START request from being sent by the new AP that the client roams to. This is the primary action of this new feature.
In addition, the session-ID, TX/RX packets information is also migrated to the new AP.
View original

3 replies

Userlevel 5
Aviv, it's not an update to the actual roaming algorithms or procedure. It's about what happens in regards to an AP initiating (not initiating) an accounting request (START) message and re-authenticating to the RADIUS accounting server, in a client roam event.

First, without this option, the accounting data is not migrated from the old AP to the new AP when a roam occurs. Only various bits of info are migrated, like the device's VLAN, it's IP address, etc. Also, an accounting STOP request is sent by the old AP to the accounting server and then an accounting START request is then sent by the new AP to the accounting server.

With this new option, a client's roam will then only continue to cause an accounting START request from the original AP and...here's the change... an accounting STOP request from the new AP *ONLY* when it roams away. This option prevents the additional START request from being sent by the new AP that the client roams to. This is the primary action of this new feature.
In addition, the session-ID, TX/RX packets information is also migrated to the new AP.
Userlevel 1
Chris -

I'm interested in this feature as well.

Is this new option ON by default or does it have to be enabled? If so, where in the GUI would I set this option?

Thanks!
Userlevel 5
Default behavior is per pre-5.9.5 behavior. This feature has to be ENABLED.
I don't have a 5.9.5 currently running to check, but I suspect that the option to enable is not yet available in the GUI and would have to be enabled in the CLI.

To enable, go into the desired WLAN profile
add the entry:
service accounting-migration-on-roam-detection

Reply