<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
<style>.hmmessage P{margin:0px;padding:0px}body.hmmessage{FONT-SIZE: 10pt;FONT-FAMILY:Tahoma}</style>Initially setup will be with same key at each site. Then it is up to their IT admin to do what ever he/she like!<br>But my question is still their or I am unable to understand (apologize for my ignorance). <br><br>The design is valid or there are still some doubt (I am asking too my question... this is my first wireless project). LWAP at remote site(s) will be able to register with WLC at head office behind the firewall (Inside Zone).<br><br>Regards,<br><br>Khalid<br><br>> Date: Wed, 20 Aug 2008 13:52:20 -0500<br>> From: smetsysocsic@gmail.com<br>> To: khalid_khursheed@hotmail.com<br>> Subject: Re: [cisco-voip] wlc 4402 and asa 5505<br>> <br>> Still a little vague to me, but I would probably agree. Are separate<br>> wireless keys required at each AP/site?<br>> <br>> -Joe C.<br>> <br>> On Wed, Aug 20, 2008 at 12:58 AM, Syed Khalid Ali<br>> <khalid_khursheed@hotmail.com> wrote:<br>> > This is what I am trying to achieve (see attached figure).<br>> ><br>> > We have 3-sites. Site-A and B are local and Site-C is remote site connected<br>> > via site-to-site VPN. The client has some sort of wireless terminals and<br>> > willing to use Cisco wireless solution. WLCs in INSIDE zone.<br>> ><br>> > Option-2 seems to be more logical.<br>> ><br>> > Need suggestions!<br>> ><br>> > Regards,<br>> > Khalid<br>> ><br>> >> Date: Tue, 19 Aug 2008 15:46:59 -0500<br>> >> From: smetsysocsic@gmail.com<br>> >> To: khalid_khursheed@hotmail.com<br>> >> Subject: Re: [cisco-voip] wlc 4402 and asa 5505<br>> >> CC: cisco-voip@puck.nether.net<br>> >><br>> >> Depends heavily on many factors, mostly the design/goals needed<br>> >> accomplished.<br>> >><br>> >> Option 1) Much like a cisco phone has the 'option 150' dhcp parameter,<br>> >> there is an 'option 43' dhcp parameter for an LWAPP (on most APs this<br>> >> isn't simply an IP address like it is on the phone, you have to pass a<br>> >> hex number that has the IP of the controller in it). In the option 43<br>> >> you specify what the IP is of the parent controller. Keep in mind that<br>> >> the ASA will have to allow traffic between the two.<br>> >><br>> >> Option 2) (My preference) first, trunk the WLC to your switch, then<br>> >> create a LWAP management VLAN that is passed to the AP - put the WLC<br>> >> and the APs in this mgmt vlan - if they are local to the same vlan,<br>> >> they'll find each other. This lwap mgmt vlan is strictly for<br>> >> communications/mgmt, and doesn't have to be passed out as a wireless<br>> >> VLAN. Then, in the controller, build your INTERFACE for this outside<br>> >> VLAN and tie it to the SSID.<br>> >><br>> >> Hope this helps.<br>> >><br>> >> -Joe C.<br>> >><br>> >> On Tue, Aug 19, 2008 at 5:59 AM, Syed Khalid Ali<br>> >> <khalid_khursheed@hotmail.com> wrote:<br>> >> > hi,<br>> >> ><br>> >> ><br>> >> > I know this is not the right place to ask, but no where else to go...<br>> >> ><br>> >> > If we have WLC 4402 setup in Inside or DMZ zone and LWAP in Outside<br>> >> > zone,<br>> >> > will it be able to register with wireless lan controller?<br>> >> ><br>> >> > regards,<br>> >> ><br>> >> > Khalid<br>> >> ><br>> >> > ________________________________<br>> >> > Connect to the next generation of MSN Messenger Get it now!<br>> >> > _______________________________________________<br>> >> > cisco-voip mailing list<br>> >> > cisco-voip@puck.nether.net<br>> >> > https://puck.nether.net/mailman/listinfo/cisco-voip<br>> >> ><br>> >> ><br>> ><br>> > ________________________________<br>> > Explore the seven wonders of the world Learn more!<br><br /><hr />Discover the new Windows Vista <a href='http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE' target='_new'>Learn more!</a></body>
</html>