Kristjan that is the common configuration methodology used. http://blakekrone.com/2011/03/10/cisco-officeextend-always-connected
Generally speaking the issue you talked about with the NAT address won't happen as your DMZ wouldn't have APs joined to it. But there is a CLI command to allow the WLC to be found via both NAT and non-NAT addresses. On Jun 28, 2012, at 10:07 AM, Kristján Ólafur Eðvarðsson <[email protected]> wrote: > Has anyone tried to use the same controller for Office Extend and Guest > tunneling. > > I am thinking it could be on a DMZ. And you would have some HQ controllers > sending the > guest tunnels to the DMZ controller. This is all normal. > > But it seems to me that a DMZ controller could also serve Office extend AP´s > and send them over to the > HQ controllers via similar method, but this time the Anchor would be the HQ > Controller(s). > > Has anyone tested this yet and made it work ? > > I also saw there is a limitation with the natted address. Say you have a > 10.10.10.10 on your office Extend WLC managment address. > And you configure the natted address (configured under managment interface) > to some public address. Lets say 157.157.157.157. > For AP´s that know your controller as 10.10.10.10. Will they stop working and > try 157.157.157.157 aswell ? because in a case like > that they probably won´t have IP connectivity this way. > > I read on the forums that this might be an issue. But I wonder if something > new has changed in recent codes e.t.c. > > regards. Kristjan > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
