<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: LAP behind WGB in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/lap-behind-wgb/m-p/1268098#M185272</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You may want to test this out and see your results.&lt;/P&gt;&lt;P&gt;In theory it looks like it could work, but may not be the best design if it did work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So now I ask you a question:&lt;/P&gt;&lt;P&gt;Is the WGB a Cisco AP? If so, why not try something like Indoor Mesh with ethernet bridging?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WLC - LAN - RAP1 - MAP1 - LAN - LAP1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This way the LAP1 is not a WGB Client of the controller and instead its packets are egressing from RAP1 to go across the LAN to WLC like normal. Also gives you vlan support on this wired section off the WGB&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just my $.02&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(design requires 5.2 or 6.0)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 03 Sep 2009 02:28:26 GMT</pubDate>
    <dc:creator>weterry</dc:creator>
    <dc:date>2009-09-03T02:28:26Z</dc:date>
    <item>
      <title>LAP behind WGB</title>
      <link>https://community.cisco.com/t5/wireless/lap-behind-wgb/m-p/1268096#M185270</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to make next design --&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*WLC*--LAN--*LAP1* --WLAN-- *WGB*--LAN--*LAP2*&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, is there any limitations, will LAP2 reach the WLC?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Teemu&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 00:58:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lap-behind-wgb/m-p/1268096#M185270</guid>
      <dc:creator>tvaris</dc:creator>
      <dc:date>2021-07-04T00:58:58Z</dc:date>
    </item>
    <item>
      <title>Re: LAP behind WGB</title>
      <link>https://community.cisco.com/t5/wireless/lap-behind-wgb/m-p/1268097#M185271</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can configure an access point to operate as a workgroup bridge so that it can provide wireless connectivity to a lightweight access point on behalf of clients that are connected by Ethernet to the workgroup bridge access point. When you configure the access point to operate as a workgroup bridge and connect to a Cisco Unified network, it can provide wireless connectivity to wired clients that are connected by Ethernet to the workgroup bridge access point.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/application/pdf/paws/100254/wgb-config.pdf" target="_blank"&gt;http://www.cisco.com/application/pdf/paws/100254/wgb-config.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Sep 2009 13:18:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lap-behind-wgb/m-p/1268097#M185271</guid>
      <dc:creator>vkapoor5</dc:creator>
      <dc:date>2009-09-01T13:18:36Z</dc:date>
    </item>
    <item>
      <title>Re: LAP behind WGB</title>
      <link>https://community.cisco.com/t5/wireless/lap-behind-wgb/m-p/1268098#M185272</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You may want to test this out and see your results.&lt;/P&gt;&lt;P&gt;In theory it looks like it could work, but may not be the best design if it did work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So now I ask you a question:&lt;/P&gt;&lt;P&gt;Is the WGB a Cisco AP? If so, why not try something like Indoor Mesh with ethernet bridging?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WLC - LAN - RAP1 - MAP1 - LAN - LAP1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This way the LAP1 is not a WGB Client of the controller and instead its packets are egressing from RAP1 to go across the LAN to WLC like normal. Also gives you vlan support on this wired section off the WGB&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just my $.02&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(design requires 5.2 or 6.0)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Sep 2009 02:28:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lap-behind-wgb/m-p/1268098#M185272</guid>
      <dc:creator>weterry</dc:creator>
      <dc:date>2009-09-03T02:28:26Z</dc:date>
    </item>
    <item>
      <title>Re: LAP behind WGB</title>
      <link>https://community.cisco.com/t5/wireless/lap-behind-wgb/m-p/1268099#M185273</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt; I just was trying to set this up and had no luck, I'm not sure my APs support the RAP and MAP.&lt;/P&gt;&lt;P&gt;WLC 4404 controller 5.2.198&lt;/P&gt;&lt;P&gt;AP are both AIR-LAP1242AG-A-K9  would you know if these are OK?&lt;/P&gt;&lt;P&gt;I followed docs for doing MAC Filtering, added 1242 ethernet addresses, did the set role and the APs reboot but get nothing when I try to bring up the radio link between RAP and MAP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks!&lt;/P&gt;&lt;P&gt;jim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Sep 2009 10:04:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lap-behind-wgb/m-p/1268099#M185273</guid>
      <dc:creator>jmglass</dc:creator>
      <dc:date>2009-09-03T10:04:27Z</dc:date>
    </item>
    <item>
      <title>Re: LAP behind WGB</title>
      <link>https://community.cisco.com/t5/wireless/lap-behind-wgb/m-p/1268100#M185274</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1242 is correct.&lt;/P&gt;&lt;P&gt;Set the role to "bridge" and then it some reboot as a mesh AP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;go to the mesh tab on the AP configuration and make sure it is set for RAP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Get the second AP on the controller, convert it to mesh, and then when it joins the controller again, make sure it is MAP instead of RAP (mesh instead of root).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After that, they should connect to each other assuming you have your 5ghz antennas installed and enabled... and assuming you've unplugged the wired interface of the AP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;turn on ethernet bridging once the link is up to do bridging across the link&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Sep 2009 13:22:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lap-behind-wgb/m-p/1268100#M185274</guid>
      <dc:creator>weterry</dc:creator>
      <dc:date>2009-09-03T13:22:16Z</dc:date>
    </item>
    <item>
      <title>Re: LAP behind WGB</title>
      <link>https://community.cisco.com/t5/wireless/lap-behind-wgb/m-p/1268101#M185275</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WGB is a Cisco AP, but we are using 4.2 code and it has been freezed for that. That's why indoor mesh is not the option. (By the way, am I right that the should purchase the lisence for indoor mesh)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also thought that design should work, but when I tested it first time, result was negative. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Sep 2009 16:55:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lap-behind-wgb/m-p/1268101#M185275</guid>
      <dc:creator>tvaris</dc:creator>
      <dc:date>2009-09-03T16:55:53Z</dc:date>
    </item>
  </channel>
</rss>

