If you are going to use the ICA client, you will need to firewall your wireless network from your private, wired network.
This might not be necessary if you are using a VPN appliance with firewall features built-in, like the Cisco and Nortel boxes.
Personally, I can't stand remote user VPNs, so I would recommend using secure ICA and firewall the wireless equipment. You can use a spare firewall interface for this, but make sure that the firewall policy only permits tcp 1494 from the wireless network to the private network. You will need to configure your ICA client with an IP address, not a DNS name (because you aren't permitting DNS traffic). Do not permit any traffic from the wireless network to the Internet or any other networks - let them get Internet surf in the ICA window.
Most people would argue for IPSEC VPN with 3DES. I think that is definatly more secure, but will require more planning and support. The ICA client is much easier to install than most RUVPN clients and you don't need to worry about cached logon credentials, password sync, etc. Bottom line: ICA is going to be much easier to maintain and manage and the users will probably find it a lot easier to use.
You may also consider using two-factor authentication with either solution. That would bring the risk down considerably. SecurID agents work on Citrix and in most RUVPNs.
IntroductionHow to use the Wireless LAN Controller Configuration Analyzer (WLCCA)
Javier Contreras is a Senior Tech Lead for the Wireless Business Unit in Cisco, with over 2 decades of experi...
< PRE >
(#)For this reason being that : - application that doesn't use multicast, sends one copy of each packet ( data unit of traffic at layer 3 ) to each client (" who seeks the traffic ).- application that does use multicast, sends ...
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...