HREAP question

Unanswered Question
Jun 19th, 2009
User Badges:

Okay I have a WiSM with just one WLAN defined on a local segment.


I am trying to install an AP across the WAN and leverage HREAP. The AP gets a local IP no problem but the WAN tunnels the WLAN segment from the controller back to the HREAP AP.


What do I need to do such that the HREAP AP addresses clients from the local segment.


(I do not have WCS yet.)


Thanks.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
scott.hammond Fri, 06/19/2009 - 04:32
User Badges:

Yes


and I have read that, it seems to make no mention of WLANs on that document.


Since the WLAN is tied to a specific interface or VLAN do I have to build a new WLAN and tie it to something different for an HREAP AP to use the local segment?


Or is that local switching supposed to overide that?

naks Fri, 06/19/2009 - 05:23
User Badges:

Hi,


Just to get a clear picture on what you are trying, are you saying that with local switching enabled, the traffic from your clients still go through the WLC instead of getting locally switched?


Can you paste the config of the switch port on which this h-reap is connected and also the controller config?


Regards,


Nagendra

Scott Fella Sat, 06/20/2009 - 14:30
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

Scott,


The reason traffic is going back to th WLC, is probably because you didn't define the native and local vlan's on the h-reap ap. On the h-reap ap there is an h-reap tab. There you need to define the native vlan which will be the vlan the ap belongs to. That vlan will need to be set as the native vlan on the trunk port. Then you need to go back to the h-reap ap h-reap tab and set the local vlan id for the specific WLAN. On the local network you will need to create a vlan for that WLAN or put them on an existing. I prefer to keep wireless seperate from other subnets.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode