If you configure "infrastructure-client" on the root AP radio, and you configure the WGB for "station-role workgroup-bridge multicast mode infrastructure," you should not receive those error message. If "infrastructure-client" is on the root AP, and the WGB is configured for "multicast mode client," then you will receive those messages. In that mode, the WGB should, as the message says, drop multicast and broadcast traffic, since it is receiving a packet with 4 addresses instead of the 3 that it is expecting.
Are you saying that your multicast MoH worked, even with that error message? Jason Boyers - CCIE #26024 (Wireless) Technical Instructor - IPexpert, Inc. Mailto: *[email protected]* 2011/6/8 Kristján Ólafur Eðvarðsson <[email protected]> > Hey again, > > > > I managed to put a 7960 phone on the VLAN998 behind > > the WGB wired switch. To register over the bridge link to a CME box > > Configured for MOH via Multicast. I used a 7921 to call between > > to test multicast MOH between. I could use the root to connect the 7921. > > I tested this with one VLAN using the work-group bridge client vlan 998 > command. > > > > If people are interested in the configuration you can post me. > > > > I am next going to try out LAB 3.9 that Vit mentioned. See if I can get it > working. > > But I don´t understand why people talk about workgroup-bridge client vlan > command > > in that perspective, because I don´t think it is of any use in this 3.9 > lab. And the > > question doesn´t seem to demand it. I haven´t looked at the DSG yet. I will > > do that after I figure it out, of course! :D > > > > regards. Kristjan > > > > p.s > > > > Interesting to see if I use the various workgroup-bridge multicast mode > client or infrastructure > > I get this message on the WGB console if I configure either way: > > > > *Mar 2 00:14:05.486: %DOT11-6-MCAST_DISCARD: client mode multicast packets > are discarded in infrastructure mode multicast mode > > > > or : > > > > *Mar 2 00:15:35.809: %DOT11-6-MCAST_DISCARD: client mode multicast packets > are discarded in infrastructure mode multicast mode > > > > with only workgroup-bridge mode. This log disappears. > > > > Jason can you explain what this means for your traffic? > > > > > > > > > > > > *From:* Kristján Ólafur Eðvarðsson > *Sent:* 7. júní 2011 23:14 > *To:* Vit > *Cc:* Jason Boyers; [email protected]; Kristján Ólafur > Eðvarðsson > *Subject:* RE: [OSL | CCIE_Wireless] 1. Re: [CCIE Wireless] Autonomous > Mode Configs (Vit) > > > > In this case, I had another excersise in mind from Jason´s bootcamp. > > > > But I will be glad to look at 3.8 myself > > and see If I understand it and post some thoughts :D > > > > > > regards. Kristjan > > > > *From:* Vit [mailto:[email protected]] > *Sent:* 7. júní 2011 17:00 > *To:* Kristján Ólafur Eðvarðsson > *Cc:* Jason Boyers; [email protected] > *Subject:* Re: [OSL | CCIE_Wireless] 1. Re: [CCIE Wireless] Autonomous > Mode Configs (Vit) > > > > Hi Kristjan, > > Firstly, many thanks for testing and sharing the configs! > > Yes, this works perfectly well when you use 'bridge-group 1' associated > with the Vlan998 on the root AAP :) Actually, even if you do not specify > 'work clien 998' on WGB, its interface BVI1 will still get an ip address > from a DHCP server. > > My issue arrises from Lab 3.8. According to requirements (or it is just my > wrong understanding), Vlan 110 on the Root AP has to be associated with the > bridge-group 1, because this is a management Vlan. The Lab 3.8 does not > mention to use 'work client-vlan 11' on the WGB, I decided to go extra mile > and got stuck.... Also, looked at the configs provided by Jason ( > http://onlinestudylist.com/archives/ccie_wireless/2011-March/002018.html), > but they do not work for me. > > May be I'm missing something... but can someone try the configs WGB-client > taken from the link above please? > > >>* WGB with Client-VLAN* > > >>* ROOT AP* > > >>* dot11 ssid test* > > >>* vlan 20* > > >>* auth open* > > >>* !* > > >>* int dot 0* > > >>* ssid test* > > >>* station-role root* > > >>* !* > > >>* int d0.20* > > >>* encap dot 20* > > >>* bridge-group 20* > > >>* !* > > >>* int f0.20* > > >>* encap dot 20* > > >>* bridge-group 20* > > >>* * > > >>* WGB CLIENT* > > >>* dot11 ssid test* > > >>* auth open* > > >>* !* > > >>* int dot 0* > > >>* ssid test* > > >>* station-role workgroup-bridge* > > >>* !* > > >>* bridge 20 protocol ieee* > > >>* !* > > >>* workgroup-bridge client-vlan 20* > > >>* * > > >>* WG SWITCH* > > >>* int f0/2* > > >>* sw host* > > >>* sw access vlan 20* > > >>* spanning-tree bpdufilter enable* > > >> > > Many thanks. > > Regards, > Vitaly > > 2011/6/7 Kristján Ólafur Eðvarðsson <[email protected]> > > Hey Vitaly and group. > > > > I labbed this up. > > > > I got work-group bridge to work in „workgroup-bridge client vlan 998“ mode > > I started to get the root ap working with the wgb-04 ssid connected to VLAN > 998 > > with DHCP server on a switch/router for the 10.10.98.0/24 subnet. > > > > I´m using 2x 1242‘s in this setup and software version of 12.3.8 JEA3 > > > > I had one problem at first, this was after enabling infrastructure-client > on the Root. > > The WGB got Dhcp address through the bridge-link but no other traffic was > working from the root. > > It was fixed after rebooting the Root. Here are the configs on the WGB and > Root. I made some fun > > addons to this excercise that you can see in next post :D > > ! > > Root config: > > ! > > hostname Root > > ! > > ! > > dot11 ssid wgb-04 > > vlan 998 > > authentication open > > ! > > ! > > interface Dot11Radio0 > > no ip address > > no ip route-cache > > ! > > ssid wgb-04 > > ! > > speed basic-1.0 2.0 5.5 6.0 9.0 11.0 12.0 18.0 24.0 36.0 48.0 54.0 > > station-role root > > infrastructure-client > > ! > > interface Dot11Radio0.998 > > encapsulation dot1Q 998 native > > no ip route-cache > > bridge-group 1 > > bridge-group 1 block-unknown-source > > no bridge-group 1 source-learning > > no bridge-group 1 unicast-flooding > > bridge-group 1 spanning-disabled > > ! > > ! > > interface FastEthernet0 > > no ip address > > no ip route-cache > > duplex auto > > speed auto > > hold-queue 160 in > > ! > > interface FastEthernet0.998 > > encapsulation dot1Q 998 native > > no ip route-cache > > bridge-group 1 > > no bridge-group 1 source-learning > > bridge-group 1 spanning-disabled > > ! > > interface BVI1 > > ip address 10.10.98.5 255.255.255.0 > > no ip route-cache > > ! > > ip default-gateway 10.10.98.1 > > ! > > bridge 1 route ip > > ! > > ---------------------------------------------- > > WGB config: > > ! > > hostname WGB > > ! > > ! > > dot11 ssid wgb-04 > > authentication open > > ! > > interface Dot11Radio0 > > no ip address > > no ip route-cache > > ! > > ssid wgb-04 > > ! > > speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 > 48.0 54.0 > > station-role workgroup-bridge > > bridge-group 1 > > bridge-group 1 spanning-disabled > > ! > > ! > > interface FastEthernet0 > > bridge-group 1 > > bridge-group 1 spanning-disabled > > hold-queue 160 in > > ! > > interface BVI1 > > ip address dhcp > > no ip route-cache > > ! > > ip default-gateway 10.10.98.1 > > ! > > cdp timer 5 > > ! > > bridge 1 route ip > > ! > > workgroup-bridge client-vlan 998 > > ! > > #The bridge gets an IP address from the switch dhcp pool. > > #My next test will be using a client on vlan 998 on the WGB connected > switch (WGB in trunk mode) > > ! > > > > > > *From:* Vit [mailto:[email protected]] > *Sent:* 6. júní 2011 23:14 > *To:* Jason Boyers > *Cc:* Kristján Ólafur Eðvarðsson; [email protected] > *Subject:* Re: [OSL | CCIE_Wireless] 1. Re: [CCIE Wireless] Autonomous > Mode Configs (Vit) > > > > Thanks Jason, > > > > Yes, I see Root AP (and connected switch) native vlan packets arriving to > the port on a switch connected to WGB and I had to configure native vlan on > this port to match the one on another side.... But no vlan 11 packets are > arriving on the switch connected to WGB... > > > > Kind regards, > > Vitaly > > 2011/6/7 Jason Boyers <[email protected]> > > Just to confirm - using the "workgroup-bridge client-vlan *x*" command > requires the following: > > > > 1) Root AP has a subinterface with the specified VLAN (mapped to the > required SSID) > > 2) If a switch is connected to the WGB, it must use a trunk. The native > VLAN should be the same as the native on the root AP (both wired and > wireless.) Otherwise, STP will detect that it is receiving BPDUs for one > "native" VLAN on a different "native" VLAN and block both. > > > > But, as you said, lab it up :) > > > > Jason Boyers - CCIE #26024 (Wireless) > > Technical Instructor - IPexpert, Inc. > Mailto: *[email protected]* > > 2011/6/6 Vit <[email protected]> > > Hey Kristjan, thanks for your response. > > > > Yes, I have a basic config on both root and WGB AAPs, e.g. auth open, ssid > and that's it :) Assigning static address to wired WGB-client didn't help as > well, so it's not DHCP-related issue. I had sub-interfaces configured on the > Root AAP, e.g. d0.11, but I believe they needed, otherwise what's the point > of having 'work clie 11' on the WGB. Could you please share a working > config, I will test if it works with wired WGB-clients and you will practice > speed ;o) > > > > Thank you. > > > > Regards, > > Vitaly > > > > 2011/6/6 Kristján Ólafur Eðvarðsson <[email protected]> > > Hey Vitaly, > > I tested this out in a lab recently. I reccon that the only command > need for the workgroup-bridge vlan x is needed. This will hide all > other stuff you would normaly do. for example int dot0.11 blablabla. > But with other stuff on the wire I didn´t test it but if the WGB was > working > from wired, I suppose clients on the WGB VLAN should work too. > > I find sometimes in cases with dhcp or other broadcast/multicast issues > the infrastructure-client command on the Root AP helps. After all > it is meant to deliver multicast (and broadcast ?) packets reliably.. > > Putting a static IP of course might help to isolate the problem to > start with and also to simplify security before troubleshooting the > DHCP related issues. I like to add the security stuff as the last step > to see all radio related stuff working first. > > my 5 cents.. > > regards. Kristjan > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 5 Jun 2011 19:57:04 +0100 > From: Vit <[email protected]> > To: [email protected] > Subject: Re: [OSL | CCIE_Wireless] [CCIE Wireless] Autonomous Mode > Configs > Message-ID: <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Guys, > > I've got a question regarding the 'workgroup-brdige client-vlan X' command > and Jason's post -> > http://onlinestudylist.com/archives/ccie_wireless/2011-March/002018.html > > Has anyone managed to get WGB with client-vlan working, e.g. wired clients > connected to the WGB are able to get ip address from a DHCP server and ping > the rest of the world through the wireless link between Root and WGB? When > I > create d0.11 subinterface on the WGB, then everything works, once I delete > d0.11 (and reboot the WGB to remove Virtual-Dot11Radio0.11) and apply 'work > clie 11' then wired clients register on the Root AAP but do not get ip > addresses... Yes, I also applied 'bridge 11 proto ieee' to WGB, but no > joy... > > Any help will be much appreciated. > > Regards, > Vitaly > > ----------------------------------------------------------------------------- > > > > -- > Regards, > Vit > > > > _______________________________________________ > 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
