wireless user connected to wireless FWSM context not able to ping gateway
We have two WLAN 4400 controllers connected to MSFC running actice/standby.
We are setting up internal & guest wireless users.Internal wireless users are terminating on MSFC & guest wireless users (vlan 24) are placed behind FWSM. We have created L2 vlan 24 in MSFC & L3 vlan 24 in FWSM.Also we have created dynamic interface in WLC & assigned vlan 24 to it.We have created DHCP pool in WLC itself for guest users & for internal wireless users we have created DHCP pool in MSFC.
Everyting works fine for internal wireless users.For guest wireless users behind FWSM (ver 2.3), they get the ip from WLC through DHCP but cannot ping the gateway.
1.Do we need any additional WLC for guest users behind FWSM ?
2.Do we need to do any configurations for such kind of scenarios?
Re: wireless user connected to wireless FWSM context not able to
Applying a firewall at the access edge to control guest access provides limited utility because it primarily acts as a simple access list, blocking access to internal IP addresses. It does not address the transport of guest client traffic across the enterprise network to the Internet edge. A better solution is to implement a dedicated guest access WLAN/service, which is natively supported in the Cisco Unified Wireless solution.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...