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
