<?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: Wireless traffic flow query in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wireless-traffic-flow-query/m-p/5263872#M281160</link>
    <description>&lt;P&gt;You are correct, it really comes down to where you want traffic to go. If you have a lot of AP’s in multiple locations, do you really want to send all your traffic to the DC? You might if you have bandwidth. Some like to keep traffic local so they can either tunnel guest traffic back to the DC using an anchor controller or maybe just use local egress. So it really comes down to your WAN and what is best for you and the amount of access points. It would be the same if you had cloud controllers in Azure or AWS, you don’t want traffic for users coming back to the controller, so you would use FlexConnect local switching.&amp;nbsp;&lt;BR /&gt;local mode = all traffic tunnnels back to the controller&lt;/P&gt;
&lt;P&gt;flexconnect central switching = all traffic tunnels back to the controller&amp;nbsp;&lt;/P&gt;
&lt;P&gt;flexconnect local switching = traffic goes out the switch the ap is connected to&lt;/P&gt;</description>
    <pubDate>Sun, 23 Feb 2025 01:12:25 GMT</pubDate>
    <dc:creator>Scott Fella</dc:creator>
    <dc:date>2025-02-23T01:12:25Z</dc:date>
    <item>
      <title>Wireless traffic flow query</title>
      <link>https://community.cisco.com/t5/wireless/wireless-traffic-flow-query/m-p/5263869#M281159</link>
      <description>&lt;P&gt;If access point is in branch and wlc is on dc with central switching. All control and data connection should use dc internet for internet.&lt;/P&gt;&lt;P&gt;If access point is in branch and wlc is on dc with local switching. All control and data connection should be used like hair pining and use local breakout&lt;/P&gt;&lt;P&gt;note - Access points are in local mode&lt;/P&gt;</description>
      <pubDate>Sun, 23 Feb 2025 00:40:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-traffic-flow-query/m-p/5263869#M281159</guid>
      <dc:creator>palani2010</dc:creator>
      <dc:date>2025-02-23T00:40:29Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless traffic flow query</title>
      <link>https://community.cisco.com/t5/wireless/wireless-traffic-flow-query/m-p/5263872#M281160</link>
      <description>&lt;P&gt;You are correct, it really comes down to where you want traffic to go. If you have a lot of AP’s in multiple locations, do you really want to send all your traffic to the DC? You might if you have bandwidth. Some like to keep traffic local so they can either tunnel guest traffic back to the DC using an anchor controller or maybe just use local egress. So it really comes down to your WAN and what is best for you and the amount of access points. It would be the same if you had cloud controllers in Azure or AWS, you don’t want traffic for users coming back to the controller, so you would use FlexConnect local switching.&amp;nbsp;&lt;BR /&gt;local mode = all traffic tunnnels back to the controller&lt;/P&gt;
&lt;P&gt;flexconnect central switching = all traffic tunnels back to the controller&amp;nbsp;&lt;/P&gt;
&lt;P&gt;flexconnect local switching = traffic goes out the switch the ap is connected to&lt;/P&gt;</description>
      <pubDate>Sun, 23 Feb 2025 01:12:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-traffic-flow-query/m-p/5263872#M281160</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2025-02-23T01:12:25Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless traffic flow query</title>
      <link>https://community.cisco.com/t5/wireless/wireless-traffic-flow-query/m-p/5263873#M281161</link>
      <description>&lt;P&gt;Thanks Scott.&lt;/P&gt;&lt;P&gt;Flex connect local switching means only control traffic sends to wlc and data traffic uses local egress direct without sending to wlc.&lt;/P&gt;</description>
      <pubDate>Sun, 23 Feb 2025 01:17:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-traffic-flow-query/m-p/5263873#M281161</guid>
      <dc:creator>palani2010</dc:creator>
      <dc:date>2025-02-23T01:17:37Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless traffic flow query</title>
      <link>https://community.cisco.com/t5/wireless/wireless-traffic-flow-query/m-p/5263876#M281162</link>
      <description>&lt;P&gt;That is correct. That way customers have options depending on their use case. I have implemented both and in some cases like in a campus, you can have multiple controllers and all the APs in the campus buildings would tie back to the controller. You don’t need a controller in every building, but you can, so you decide also depending on your budget.&lt;/P&gt;</description>
      <pubDate>Sun, 23 Feb 2025 01:39:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-traffic-flow-query/m-p/5263876#M281162</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2025-02-23T01:39:29Z</dc:date>
    </item>
  </channel>
</rss>

