<?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: IW6300 internal switching bug? in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/iw6300-internal-switching-bug/m-p/4667855#M245048</link>
    <description>&lt;P&gt;Do you maybe have this blocked on the SSID (P2P blocking action)? I'm not sure if this would stop the communication with a directly attached wired client though, I don't have an IW6300 for testing.&lt;/P&gt;</description>
    <pubDate>Thu, 11 Aug 2022 14:10:20 GMT</pubDate>
    <dc:creator>patoberli</dc:creator>
    <dc:date>2022-08-11T14:10:20Z</dc:date>
    <item>
      <title>IW6300 internal switching bug?</title>
      <link>https://community.cisco.com/t5/wireless/iw6300-internal-switching-bug/m-p/4667453#M245033</link>
      <description>&lt;P&gt;Hello everyone!&lt;BR /&gt;Has anyone used the IW6300 and encountered the following bug?&lt;BR /&gt;In Flex mode, I have the SSID "alpha" mapped to VLAN 611, and in the internal switch of the IW6300 on port 2, I have the access VLAN 611 defined.&lt;BR /&gt;The first thing that one assumes, is that a WiFi user associated to SSID "alpha", should be able to communicate (at least with a ping) with the user wired to port 2 that is in the access VLAN 611, but the reality is that it will not be able to.&lt;BR /&gt;Now, let's use port 1 of the IW6300 switch in trunk mode and connect it to another L2 switch. If I connect a user on this second switch in access VLAN 611, now the WiFi user of SSID "alpha" will be able to connect (at least with a ping) with this wired user.&lt;BR /&gt;I ask, shouldn't the IW6300's integrated switch be able to make this connection between a wireless user and a wired user on the internal switch if at the end of the path they both share VLAN 611?&lt;BR /&gt;Experience tells me that this does not happen and that unless someone points out otherwise, this is a tremendous bug in the IW6300.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Nor.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Aug 2022 20:56:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/iw6300-internal-switching-bug/m-p/4667453#M245033</guid>
      <dc:creator>norberto.padin</dc:creator>
      <dc:date>2022-08-10T20:56:05Z</dc:date>
    </item>
    <item>
      <title>Re: IW6300 internal switching bug?</title>
      <link>https://community.cisco.com/t5/wireless/iw6300-internal-switching-bug/m-p/4667855#M245048</link>
      <description>&lt;P&gt;Do you maybe have this blocked on the SSID (P2P blocking action)? I'm not sure if this would stop the communication with a directly attached wired client though, I don't have an IW6300 for testing.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Aug 2022 14:10:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/iw6300-internal-switching-bug/m-p/4667855#M245048</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2022-08-11T14:10:20Z</dc:date>
    </item>
    <item>
      <title>Re: IW6300 internal switching bug?</title>
      <link>https://community.cisco.com/t5/wireless/iw6300-internal-switching-bug/m-p/4668016#M245057</link>
      <description>&lt;P&gt;Confirmed, it is a bug in Marvel´s chipset.&amp;nbsp;&lt;BR /&gt;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvz92467" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvz92467&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Aug 2022 21:51:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/iw6300-internal-switching-bug/m-p/4668016#M245057</guid>
      <dc:creator>norberto.padin</dc:creator>
      <dc:date>2022-08-11T21:51:51Z</dc:date>
    </item>
  </channel>
</rss>

