How does the anchor controller work with regards to the web traffic

[carl_townshend]

Hi all

I am configuring an anchor controller for my guest wireless internet access.

Firstly, does the config need to have all the same config, SSID's etc on it, the same as the other controllers, or is it a minimal config?

also, how does the web traffic travel through, does the anchor controller literally act as a proxy for the web traffic? and if so on my firewall is the web traffic all sourced from the anchor controllers IP address?

Many thanks

Carl

[Stephen Rodriguez]

DMZ Anchor.

ip address 172.16.1.0/23.  Plenty of space for the client.

Local

ip address 192.168.1.0/24.  No layer 2 VLAN associated, or you can create one and at L3 ip route 192.168.1.0/24 null 0, to stop them from getting anywhere incase the anchor breaks.

Client associates, to the local, is pushed across the mobiltiy tunnel to the DMZ, where they get IP 172.16.1.50/24.  As this is where the IP subnet resides, what ever routing and FW policies you allow are followed.

No Anchor:

Local WLC

Ip address 192.168.1.0/24.  Client gets an address in this IP subnet, and foloows the local routing rules you have defined for the subnet.

Steve