<?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 Hey, in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/p2p-blocking-action-behavior/m-p/3024680#M216804</link>
    <description>&lt;P&gt;Hey,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;It is fairly straight forward when using centrally switched WLANs or with APs in local mode on the same WLC. If you apply P2P Blocking action of&amp;nbsp;&lt;STRONG&gt;drop&amp;nbsp;&lt;/STRONG&gt;globally on your WLAN this will stop the APs/WLC forwarding packets between clients attached to all APs.&lt;/P&gt;
&lt;P&gt;This does not apply to multicast traffic however.&lt;/P&gt;
&lt;P&gt;Ric&lt;/P&gt;</description>
    <pubDate>Wed, 08 Mar 2017 02:26:42 GMT</pubDate>
    <dc:creator>Ric Beeching</dc:creator>
    <dc:date>2017-03-08T02:26:42Z</dc:date>
    <item>
      <title>P2P Blocking Action behavior</title>
      <link>https://community.cisco.com/t5/wireless/p2p-blocking-action-behavior/m-p/3024679#M216803</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I am looking to isolate client traffic for a certain WLAN. I want to deny traffic from clients on the same WLAN, across all APs.&lt;/P&gt;
&lt;P&gt;Can anyone explain how p2p blocking action works? Are there any considerations? Please let me know if you need more information,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;WLC2504 - FW version&amp;nbsp;&lt;SPAN&gt;7.6.120.0&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 13:40:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/p2p-blocking-action-behavior/m-p/3024679#M216803</guid>
      <dc:creator>mpitts</dc:creator>
      <dc:date>2021-07-05T13:40:21Z</dc:date>
    </item>
    <item>
      <title>Hey,</title>
      <link>https://community.cisco.com/t5/wireless/p2p-blocking-action-behavior/m-p/3024680#M216804</link>
      <description>&lt;P&gt;Hey,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;It is fairly straight forward when using centrally switched WLANs or with APs in local mode on the same WLC. If you apply P2P Blocking action of&amp;nbsp;&lt;STRONG&gt;drop&amp;nbsp;&lt;/STRONG&gt;globally on your WLAN this will stop the APs/WLC forwarding packets between clients attached to all APs.&lt;/P&gt;
&lt;P&gt;This does not apply to multicast traffic however.&lt;/P&gt;
&lt;P&gt;Ric&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 02:26:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/p2p-blocking-action-behavior/m-p/3024680#M216804</guid>
      <dc:creator>Ric Beeching</dc:creator>
      <dc:date>2017-03-08T02:26:42Z</dc:date>
    </item>
    <item>
      <title>Thanks Ric!</title>
      <link>https://community.cisco.com/t5/wireless/p2p-blocking-action-behavior/m-p/3024681#M216805</link>
      <description>&lt;P&gt;Thanks Ric!&lt;/P&gt;
&lt;P&gt;What if I have APs in flexconnect with local switching?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I am hearing conflicting information.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I appreciate you answering my questions!&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 02:35:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/p2p-blocking-action-behavior/m-p/3024681#M216805</guid>
      <dc:creator>mpitts</dc:creator>
      <dc:date>2017-03-08T02:35:20Z</dc:date>
    </item>
    <item>
      <title>No probs,</title>
      <link>https://community.cisco.com/t5/wireless/p2p-blocking-action-behavior/m-p/3024682#M216806</link>
      <description>&lt;P&gt;No probs,&lt;/P&gt;
&lt;P&gt;For your version of software it appears that P2P blocking is supported on locally switched WLANs:&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;Peer-to-peer blocking is supported for clients that are associated with the local switching WLAN.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&lt;A href="http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-6/configuration-guide/b_cg76/b_cg76_chapter_01001100.html"&gt;http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-6/configuration-guide/b_cg76/b_cg76_chapter_01001100.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Ric&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 02:38:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/p2p-blocking-action-behavior/m-p/3024682#M216806</guid>
      <dc:creator>Ric Beeching</dc:creator>
      <dc:date>2017-03-08T02:38:04Z</dc:date>
    </item>
    <item>
      <title>Sadly the documentation</title>
      <link>https://community.cisco.com/t5/wireless/p2p-blocking-action-behavior/m-p/3024683#M216807</link>
      <description>&lt;P&gt;Sadly the documentation regarding P2P blocking with local switching (FlexConnect) is incomplete if you ask me. &lt;BR /&gt;&lt;BR /&gt;What really happens when you enable this feature is that "bridge-group x port-protected" is being enabled on the dot11 radio (sub) interfaces. This feature should* prevent traffic between two wireless connected end-points on the same access-point. There is no "distribution system" by which the other access-points are being informed about other guest clients. This means that you need to implement something like private VLANs on the wired side as well.&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;*: does not seem to work with latest 8.3 AirOS code, even if both clients are connected on the same radio of the access-point.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Apr 2017 23:43:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/p2p-blocking-action-behavior/m-p/3024683#M216807</guid>
      <dc:creator>Freerk Terpstra</dc:creator>
      <dc:date>2017-04-18T23:43:49Z</dc:date>
    </item>
  </channel>
</rss>

