Czy jest ktoś w stanie wyjaśnić jak dokładnie działa funkcjonalność guest tunneling i czym w praktyce różni się ona w stosunku do inter/inta controller roaming?
In auto-anchor mobility mode, a subset of a mobility group is specified as the anchor controllers for a WLAN. You can use this feature to restrict a WLAN to a single subnet regardless of a client’s entry point into the network. Usually this is used for service guests in a corporate network. In this way all guests (irrespective of the location where they connect to wireless network) will get a same subnet IP usually via a WLC in a DMZ & can only go to internet where internal network access is restricted.
When a client first associate to a WLC of a mobility group that has been pre-configured as a mobility anchor for a WLAN, the client associate to the controller locally.Clients can be anchored only to pre-configured anchor controllers of the WLAN. (In guest service usually DMZ WLC). The client associated controller is announced this to the rest of the controller in the mobility list. If the announcement is not answered, the controller contacts one of the anchor controllers configured for the WLAN and create a foreign session for the client on the local switch. Packets from the client are encapsulated through a mobility tunnel using EoIP (IP protocol 97) & sent to the anchor controller. Here is the typical use case for Auto Anchor deployment.
Tak jak w przypadku normalnego roamingu tworzony jest tunel to kontrolera anchor.
The beauty of Auto-Anchor is that the end user will automatically connect to the WLAN as if they were in their own office.
Czy ta funkcjonalność nie jest ograniczona do broadcastowania konkretnego SSID?
