Tags

, ,

Work Group Bridges (WGB) are Autonomous APs configured as clients. These WGB APs are used to relay traffic from non-802.11 clients to wireless infrastructure. This is different to normal wireless bridge where wireless bridge is used for trunking multiple vlan across a wireless link (think of wireless trunk). On the other hand WGB is used to connect non-802.11 devices into wireless network.

WGB can connect  to autonomous AP or Lightweight AP like any other client.In the following lab set up I have used Autonomous AP as Root (It can be LWAP as well)Auto-WGB-01

First scenario is WGB is connected to a dot1q capable switch where you want to have wired clients in different vlans. Vlan 110 would be the native vlan & therefore Fa0/2 of AS01 & G0/8 of AS02 are configured as trunk port with native vlan 110. In this lab I have configured 3 vlans (110,12,15) & related sub interfaces on root AP & WGB. Vlan 110 is configured as native VLAN & it is assigned to infrastructure SSID. Under Radio interface you have to configure “infrastructure-client” command in order to WGB to associate with infrastructure SSID. Also this will allow multicast/ broadcast packets to WGB are acknowledged by WGB.(make multicast/broadcast reliable). Here is the full configuration of Root AP.

hostname AAP1
!
dot11 ssid WGB
   vlan 110
   authentication open 
   infrastructure-ssid 
!
interface Dot11Radio0
 ssid WGB
 station-role root
 infrastructure-client
!
interface Dot11Radio0.12
 encapsulation dot1Q 12
 bridge-group 12
!
interface Dot11Radio0.15
 encapsulation dot1Q 15
 bridge-group 15
!
interface Dot11Radio0.110
 encapsulation dot1Q 110 native
 bridge-group 1
!
interface FastEthernet0.12
 encapsulation dot1Q 12
 bridge-group 12
!
interface FastEthernet0.15
 encapsulation dot1Q 15
 bridge-group 15
!
interface FastEthernet0.110
 encapsulation dot1Q 110 native
 bridge-group 1
!
interface BVI1
 ip address 10.10.110.101 255.255.255.0
!
ip default-gateway 10.10.110.3

In the WGB, we have to specify the role under radio interface by using the command “station-role workgroup-bridge“. This makes this AP acting as special type of client to the root AP. Here is the complete configuration of WGB.

hostname AAP2
!
dot11 ssid WGB
   vlan 110
   authentication open 
   infrastructure-ssid
!         
interface Dot11Radio0
 ssid WGB
 station-role workgroup-bridge
!
interface Dot11Radio0.12
 encapsulation dot1Q 12
 bridge-group 12
!
interface Dot11Radio0.15
 encapsulation dot1Q 15
 bridge-group 15
!
interface Dot11Radio0.110
 encapsulation dot1Q 110 native
 bridge-group 1
!
interface FastEthernet0.12
 encapsulation dot1Q 12
 bridge-group 12
!
interface FastEthernet0.15
 encapsulation dot1Q 15
 bridge-group 15
!         
interface FastEthernet0.110
 encapsulation dot1Q 110 native
 bridge-group 1
!
interface BVI1
 ip address 10.10.110.102 255.255.255.0
!
ip default-gateway 10.10.110.3

You can verify the wired clients association to this WGB by issuing “show dot11 association” command. In my example two laptops connected to AS02 two switch ports which is configured for Vlan 12 & Vlan 15. They will obtain IP from DHCP server (sits behind DS01) & usually within 1-2 minutes. (Generally it is slow & allow enough time prior to come to conclusion it is not working). You can ping any IPs from these machines & that prove it has network connectivity to rest of the network.

AAP1#sh dot11 ass
802.11 Client Stations on Dot11Radio0: 
SSID [WGB] :

MAC Address    IP address      Device        Name            Parent         State     
0019.30dd.9b74 10.10.110.102   WGB           AAP2            self           Assoc    
001f.1618.dfec 10.10.15.54     WGB-client    -               0019.30dd.9b74 Assoc    
5c26.0a65.8f37 10.10.12.51     WGB-client    -               0019.30dd.9b74 Assoc    

AAP2#sho dot11 ass
802.11 Client Stations on Dot11Radio0: 
SSID [WGB] : 

MAC Address    IP address      Device        Name            Parent         State     
001b.2a30.48b0 10.10.110.101   11g-bridge    AAP1            -              Assoc

Now we will look at next scenario where WGB is connected to non-trunking capable switch/hub.See the diagram below.Auto-WGB-02

In this case you need to configure “workgroup-bridge client-vlan x” where all the devices connected to WGB via Hub will be on vlan x. In my example I will configure all ports in my 8 port switch (AS02) in to vlan 15.

When I connected my laptops into G0/2 & G0/6 they could not get the IP from DHCP server. why ?

When I checked spanning tree for vlan 15 on this 8 port switch I can see G0/8 in “Block” state. This is due to G0/8 receive dot1q frames from the autonomous AP & switch is intelligent enough to detect these & put the port into “Block” state. If you use a hub, it should not behave like this & straight away you should get IPs to your devices.

CAT4(config-if-range)#do sh span vlan 15
VLAN0015
  Spanning tree enabled protocol ieee
  Root ID    Priority    32783
             Address     58bf.ea59.f800
             This bridge is the root
             Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec

  Bridge ID  Priority    32783  (priority 32768 sys-id-ext 15)
             Address     58bf.ea59.f800
             Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec
             Aging Time  15  sec

Interface           Role Sts Cost      Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Gi0/2               Desg FWD 4         128.2    P2p 
Gi0/8               Desg BKN*19        128.8    P2p *TYPE_Inc

You can simply disable Spanning Tree on this vlan by issueing “ no spanning-tree vlan 15” command. Then immediately you would see two laptops will associate to workgroup bridge & get correct IP from DHCP server.

AAP1#sh dot11 ass
802.11 Client Stations on Dot11Radio0: 
SSID [WGB] : 

MAC Address    IP address      Device        Name            Parent         State     
0019.30dd.9b74 10.10.110.102   WGB           AAP2            self           Assoc    
001f.1618.dfec 10.10.15.54     WGB-client    -               0019.30dd.9b74 Assoc    
5c26.0a65.8f37 10.10.15.55     WGB-client    -               0019.30dd.9b74 Assoc

We will see how WGB connect to LWAP in next post on this topic.

Related Posts

1. Lightweight to Autonomous (vice versa) Conversion
2. Multiple SSID Config on Autonomous AP
3. Autonomous AP – Wireless Bridges
4. Autonomous AP – Repeater