<?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: Workgroup bridge timing out in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/workgroup-bridge-timing-out/m-p/1120594#M187117</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I didn't think workgroup bridge allowed wireless clients associate to it. I don't want anyone to actually associate to the AP. If I changed it to non-root, wouldn't it allow wireless clients to associate like a normal AP, and why would this be able to resolve my issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 10 Dec 2008 23:00:20 GMT</pubDate>
    <dc:creator>John Blakley</dc:creator>
    <dc:date>2008-12-10T23:00:20Z</dc:date>
    <item>
      <title>Workgroup bridge timing out</title>
      <link>https://community.cisco.com/t5/wireless/workgroup-bridge-timing-out/m-p/1120592#M187114</link>
      <description>&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a workgroup bridge with some clients behind it. Everything works until the access point disassociates with the parent overnight when no traffic is seen. I've tried to change the parent's default and max activity-timeout times to 86400, but that didn't help. It went down this morning around 5AM, but then came up around 8:30AM. I assume this is when people are coming into that building. Is there a way to keep this from happening? Do I need to also change the activity-timeout on the WGB-client?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jul 2021 23:52:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/workgroup-bridge-timing-out/m-p/1120592#M187114</guid>
      <dc:creator>John Blakley</dc:creator>
      <dc:date>2021-07-03T23:52:23Z</dc:date>
    </item>
    <item>
      <title>Re: Workgroup bridge timing out</title>
      <link>https://community.cisco.com/t5/wireless/workgroup-bridge-timing-out/m-p/1120593#M187116</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;why do you want to set it to workgroup bridge , why not root - non-root setup. It would still function the same way.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Dec 2008 22:05:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/workgroup-bridge-timing-out/m-p/1120593#M187116</guid>
      <dc:creator>rnigam</dc:creator>
      <dc:date>2008-12-10T22:05:32Z</dc:date>
    </item>
    <item>
      <title>Re: Workgroup bridge timing out</title>
      <link>https://community.cisco.com/t5/wireless/workgroup-bridge-timing-out/m-p/1120594#M187117</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I didn't think workgroup bridge allowed wireless clients associate to it. I don't want anyone to actually associate to the AP. If I changed it to non-root, wouldn't it allow wireless clients to associate like a normal AP, and why would this be able to resolve my issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Dec 2008 23:00:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/workgroup-bridge-timing-out/m-p/1120594#M187117</guid>
      <dc:creator>John Blakley</dc:creator>
      <dc:date>2008-12-10T23:00:20Z</dc:date>
    </item>
  </channel>
</rss>

