WGB con AP NO CISCO

 WGB con AP NO CISCO.

Con la opción  Workgroup de cisco podemos conectar varios host, maquinas virtuales o equipos que no disponen de opción a conexión wireless.
Desde la pádina de cisco    Ejemplos de configuración de Cisco WGB

   Podemos ver como podemos configurar esta opción.
    Con este método podemos obetener una rápida solución de conexión de máquinas virtuales, hypervisores (VMware, hyper-V), conexión de equipos que no disponen de opción wifi.

El problema viene cuando queremos realizar esta opción con AP's  no cisco.
Primer problema: Los Ap 's No cisco no disponen de la opción WGB bridge.
Segundo Problema: Los bridge modo estación solo te permiten una dirección Ip y una MAC.

Lo que necesitamos configurar es un bridge WDS pero esta característica no viene como tal en el WLC de cisco.
http://es.wikipedia.org/wiki/Wireless_Distribution_System

  

Para poder conseguir esta opción necesitamos dos cosas:

 Controller>Multicast>Enable Global Multicast Mode

Wlan>Edit Wlan 

 

En la pestaña Advanced habilitar Passive Client

Y con esto este esquema funcionará perfectamente.

Guia de configuración Cisco Wireless LAN Controller,  Release 7.3:

 Cisco WGB non-cisco AP

"

Using Non-Cisco Workgroup Bridges

Information About Non-Cisco Workgroup Bridges

When a Cisco workgroup bridge (WGB) is used, the WGB informs the access points of all the clients that it is associated with. The controller is aware of the clients associated with the access point. When non-Cisco WGBs are used, the controller has no information about the IP address of the clients on the wired segment behind the WGB. Without this information, the controller drops the following types of messages:

• ARP REQ from the distribution system for the WGB client
• ARP RPLY from the WGB client
• DHCP REQ from the WGB client
• DHCP RPLY for the WGB client

The following are some guidelines for Non-Cisco workgroup bridges:

• The controller can accommodate non-Cisco WGBs so that the controller can forward ARP, DHCP, and data traffic to and from the wired clients behind workgroup bridges by enabling the passive client feature. To configure your controller to work with non-Cisco WGBs, you must enable the passive client feature so that all traffic from the wired clients is routed through the WGB to the access point. All traffic from the wired clients is routed through the work group bridge to the access point.
• When a WGB wired client leaves a multicast group, the downstream multicast traffic to other WGB wired clients is interrupted briefly.
• If you have clients that use PC virtualization software like VMware, you must enable this feature.

  Note	We have tested multiple third-party devices for compatibility but cannot ensure that all non-Cisco devices work. Support for any interaction or configuration details on the third-party device should be discussed with the device manufacturer.

• You must enable the passive client functionality for all non-Cisco workgroup bridges.
• You might need to use the following commands to configure DHCP on clients:
  • Disable DHCP proxy by using the config dhcp proxy disable command.
  • Enable DHCP boot broadcast by using the tconfig dhcp proxy disable bootp-broadcast enable command.

Restrictions for Non-Cisco Workgroup Bridges

• Only Layer 2 roaming is supported for WGB devices.
• Layer 3 security (web authentication) is not support for WGB clients.
• Visibility of wired hosts behind a WGB on a controller is not supported because the non-Cisco WGB device performs MAC hiding. Cisco WGB supports IAPP.
• ARP poisoning detection does not work on a WLAN when the flag is enabled.
• VLAN select is not supported for WGB clients.
• Some third-party WGBs need to operate in non-DHCP relay mode. If problems occur with the DHCP assignment on devices behind the non-Cisco WGB, use the config dhcp proxy disable and config dhcp proxy disable bootp-broadcast disable commands. The default state is DHCP proxy enabled. The best combination depends on the third-party characteristics and configuration.

"