Re: Secure private network from public with cisco 4402 controlle
You could configure the PUBLIC ssid to use address space in the 10.1.1.0 network as seen in this link http://www.cisco.com/warp/public/110/19b.html but you would still have to vlan the wlc over to that area ( normally the 10.1.1.0/24 would use a point to point link w/30 but a /24 between pix and router is "ok" ) and then you would issue ip addresses from the 10.1.1.0 scope to your PUBLIC users.
Make sure Router B does not route 10.1.1.0 internally and you would be good to go.
Replace that 501 with a ASA 5505 and you have oodles of options including support for vlan/sub-interfaces ( 501 reaches end of support next year). Then you could trunk a vlan from wlc through switch and router and terminate it(default gw) in the ASA. You could even use address space not in use elsewhere with your network to secure it even more so. You can do this with the BASE version of the 5505.
Look at figure 4.1 and substitute the word "HOME" with "PUBLIC" and you will see your network -
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...