> OK. > > The only way I found to work is using both Bridge 1 and vlan native on the > interfaces of root and WGB< example. > > root: > > ! > dot11 ssid WGB > vlan 110 > authentication open > ! > > interface Dot11Radio0 > ! > ssid WGB > ! > station-role root > infrastructure-client > ! > interface Dot11Radio0.110 > encapsulation dot1Q 110 native > bridge-group 1 > ! ! > interface FastEthernet0.110 > encapsulation dot1Q 110 native > bridge-group 1 > > WGB: > > ! > dot11 ssid WGB > authentication open > infrastructure-ssid > ! > ! > ! > interface Dot11Radio0 > ! > ssid WGB > ! > station-role workgroup-bridge multicast mode infrastructure > bridge-group 1 > ! > ! > bridge 1 protocol ieee > bridge 1 route ip > ! > workgroup-bridge client-vlan 110 > > No matter the type of multicast selected, always get an IP both WGB and > Switch in vlan 110 > > If I use a non-native vlan in bridge 1 or other bridge ID on Root AP, It > happens me the same, the WGB does not get an IP address. > > Another test made today was try the configuration posted by Stalder about > the use of subinterfaces to manage the WGB in one vlan and assing IP address > from other vlan for WGB clients. It works fine in my lab, but with multicast > infrastructure enabled if I delete the infrastructure-client from the root > AP the Catalyst linked to the root AP blocks the VLAN due to inconsistency > ID. > > CAT1# > *Mar 3 17:43:57.977: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with > inconsistent peer vlan id 12 on GigabitEthernet1/0/2 VLAN110. > *Mar 3 17:43:57.977: %SPANTREE-2-BLOCK_PVID_PEER: Blocking > GigabitEthernet1/0/2 on VLAN0012. Inconsistent peer vlan. > *Mar 3 17:43:57.977: STP: VLAN0012 Gi1/0/2 -> blocking > *Mar 3 17:43:57.977: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking > GigabitEthernet1/0/2 on VLAN0110. Inconsistent local vlan. > *Mar 3 17:43:57.977: STP: VLAN0110 sent Topology Change Notice on Po1 > *Mar 3 17:43:57.977: STP: VLAN0110 Gi1/0/2 -> blocking > Once I write again "infrastructure-client" on the radio interface of the > root ap, the spanning tree status changes to forwarding again. > CAT1# > *Mar 3 17:45:26.947: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking > GigabitEthernet1/0/2 on VLAN0012. Port consistency restored. > *Mar 3 17:45:26.947: STP: VLAN0012 Gi1/0/2 ->jump to forwarding from > blocking > *Mar 3 17:45:26.947: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking > GigabitEthernet1/0/2 on VLAN0110. Port consistency restored. > *Mar 3 17:45:26.947: STP: VLAN0110 Gi1/0/2 -> listening > *Mar 3 17:45:27.719: STP: VLAN0110 Topology Change rcvd on Gi1/0/2 > *Mar 3 17:45:27.719: STP: VLAN0110 sent Topology Change Notice on Po1 > *Mar 3 17:45:41.954: STP: VLAN0110 Gi1/0/2 -> learning > *Mar 3 17:45:42.902: STP: VLAN0110 Topology Change rcvd on Gi1/0/2 > *Mar 3 17:45:42.902: STP: VLAN0110 sent Topology Change Notice on Po1 > *Mar 3 17:45:56.961: STP: VLAN0110 sent Topology Change Notice on Po1 > *Mar 3 17:45:56.961: STP: VLAN0110 Gi1/0/2 -> forwarding > > Best Regards. > > > 2011/6/9 Vit <[email protected]> > >> Guys, >> >> I believe I have found what 'breakes' the config below. If you configure a >> link between Root AP and WGB for reliable multicasting ('*station-role >> workgr multicast mode infrastru*' on WGB) you will have to configure '* >> infrastructure-client*' on the Root AP. As soon as you apply '* >> infrastructure-client*,' traffic is not passing through the link between >> Root AP and WGB :) The only way to get it working with '* >> infrastructure-client*' command is to configure sub-interfaces, if you >> need clients connected to WGB to be in the specific Vlan. >> >> I may be wrong, would be nice if someone can cross check it. >> >> Many thanks. >> >> Regards, >> Vit >> >> >> On Wed, Jun 8, 2011 at 10:21 PM, Vit <[email protected]> wrote: >> >>> Hey Raul, >>> >>> The configs you provided work fine... I have noticed only one discrepancy >>> between your configs and mine when this was not working - on the Root AP you >>> have '*bridge-group 1*' associated with Dot11Radio0 and FastEthernet0, >>> in my case I had '*bridge-group 1*' associated with d0.110 and Fa0.110 >>> (both with '*enc dot 110 native*') >>> >>> To prove my theory I decided to return hardware back to non-working state >>> and associated '*bridge-group 1*' with d0.110 and Fa0.110 on the Root >>> AP. Then rebooted everything - SW1, Root AAP, WGB AAP and SW2. However, it >>> is still working... The only thing I have noticed is that the SVI11 on SW2 >>> gets ip address from a DHCP server after 1-2 minutes, and not straightaway. >>> May be this was the issue last time when it was not working as I did not >>> wait long enough.... Apart from that I do not know what was the reason it >>> was not working originally, as I used basic config and rebooted everything >>> as well - and not knowing the reason really annoys me. >>> >>> Many thanks for testing, you are a star :) Big thank you goes to Jason, >>> may thanks for sharing the Autonomous APs configs. >>> >>> Regards, >>> Vit >>> >>> On Wed, Jun 8, 2011 at 11:56 AM, Raul Manzano <[email protected]>wrote: >>> >>>> Hi Guys. >>>> >>>> The configs, following the jason´s configuration it work fine on my lab >>>> :) >>>> >>>> Root: >>>> >>>> dot11 ssid WGB >>>> vlan 12 >>>> authentication open >>>> ! >>>> interface Dot11Radio0 >>>> ! >>>> ssid WGB >>>> ! >>>> channel 2412 >>>> station-role root >>>> bridge-group 1 >>>> ! >>>> interface Dot11Radio0.12 >>>> encapsulation dot1Q 12 >>>> no ip route-cache >>>> bridge-group 12 >>>> ! >>>> ! >>>> interface FastEthernet0 >>>> bridge-group 1 >>>> ! >>>> interface FastEthernet0.12 >>>> encapsulation dot1Q 12 >>>> no ip route-cache >>>> bridge-group 12 >>>> >>>> WGB: >>>> >>>> ! >>>> dot11 ssid WGB >>>> authentication open >>>> ! >>>> ! >>>> interface Dot11Radio0 >>>> ! >>>> ssid WGB >>>> station-role workgroup-bridge >>>> bridge-group 1 >>>> ! >>>> interface FastEthernet0 >>>> bridge-group 1 >>>> ! >>>> bridge 12 protocol ieee >>>> workgroup-bridge client-vlan 12 >>>> SWITCH: >>>> >>>> vlan 12 >>>> >>>> ! >>>> interface GigabitEthernet1/0/1 >>>> switchport access vlan 12 >>>> switchport mode access >>>> spanning-tree bpdufilter enable >>>> ! >>>> ! >>>> interface Vlan1 >>>> no ip address >>>> shutdown >>>> ! >>>> interface Vlan12 >>>> ip address dhcp client-id Vlan12 >>>> ! >>>> >>>> Both The Switch and WGB gets an IP through DHCP and can ping to the >>>> network through the Workgroup bridge link. Using native vlan in root ap is >>>> also working. >>>> >>>> root: >>>> >>>> interface Dot11Radio0.12 >>>> encapsulation dot1Q 12 native >>>> no ip route-cache >>>> bridge-group 12 >>>> ! >>>> ! >>>> interface FastEthernet0.12 >>>> encapsulation dot1Q 12 native >>>> no ip route-cache >>>> bridge-group 12 >>>> ! >>>> interface FastEthernet0.110 >>>> encapsulation dot1Q 110 >>>> no ip route-cache >>>> bridge-group 1 >>>> The rest of configurations remains the same. >>>> >>>> Best regards. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 <http://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
