<?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 wireless packet flow explanation in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wireless-packet-flow-explanation/m-p/2033757#M152803</link>
    <description>&lt;P&gt;Hi My requirement is very simple , I will appreciate if someone can explain me the following concept as per the diagram mentioned below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have 2 APs AP1 and AP2, both connect to switch on port f0/1 and f0/2 , the switch f0/3 inturn connects to a router on f0/0 , router's interface f0/1 connects to another switch which is wired network with ip add 192.168.2.0/24 .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. APs broadcast 3 ssid (management , guest , cisco) respectively , how would the data flow happen for user connected to SSID cisco when pings another user connected to SSID guest , and how would data flow happen when user in SSID cisco ping a user 192.168.1.100 some user is wired network.&lt;/P&gt;&lt;P&gt;you can assume both the APs are autonomous and there is no controller.&lt;/P&gt;&lt;P&gt;I am looking for explanation in terms of frame tagging and packet encapsulation and depacsulation at various stages.&lt;/P&gt;&lt;P&gt;you can assume the IP nd vlan number on wireless network as you like.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.if you are not tired yet then one mroe question with same topology , but this time the APs are lightweight and the controller is in a different subnet 192.168.1.0 , assume that the AP is already registered with controller , now how would the same above communication happen , &lt;/P&gt;&lt;P&gt;I am looking for explanation in terms of frame tagging and packet encapsulation and depacsulation at various stages.&lt;/P&gt;&lt;P&gt;you can assume the IP and vlan number on wireless network as you like.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you can refer me some doc its fine with me , I already went through many documents and nuggets , I do have a clear picture.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
    <pubDate>Sun, 04 Jul 2021 05:53:48 GMT</pubDate>
    <dc:creator>Ambuj M</dc:creator>
    <dc:date>2021-07-04T05:53:48Z</dc:date>
    <item>
      <title>wireless packet flow explanation</title>
      <link>https://community.cisco.com/t5/wireless/wireless-packet-flow-explanation/m-p/2033757#M152803</link>
      <description>&lt;P&gt;Hi My requirement is very simple , I will appreciate if someone can explain me the following concept as per the diagram mentioned below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have 2 APs AP1 and AP2, both connect to switch on port f0/1 and f0/2 , the switch f0/3 inturn connects to a router on f0/0 , router's interface f0/1 connects to another switch which is wired network with ip add 192.168.2.0/24 .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. APs broadcast 3 ssid (management , guest , cisco) respectively , how would the data flow happen for user connected to SSID cisco when pings another user connected to SSID guest , and how would data flow happen when user in SSID cisco ping a user 192.168.1.100 some user is wired network.&lt;/P&gt;&lt;P&gt;you can assume both the APs are autonomous and there is no controller.&lt;/P&gt;&lt;P&gt;I am looking for explanation in terms of frame tagging and packet encapsulation and depacsulation at various stages.&lt;/P&gt;&lt;P&gt;you can assume the IP nd vlan number on wireless network as you like.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.if you are not tired yet then one mroe question with same topology , but this time the APs are lightweight and the controller is in a different subnet 192.168.1.0 , assume that the AP is already registered with controller , now how would the same above communication happen , &lt;/P&gt;&lt;P&gt;I am looking for explanation in terms of frame tagging and packet encapsulation and depacsulation at various stages.&lt;/P&gt;&lt;P&gt;you can assume the IP and vlan number on wireless network as you like.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you can refer me some doc its fine with me , I already went through many documents and nuggets , I do have a clear picture.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 05:53:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-packet-flow-explanation/m-p/2033757#M152803</guid>
      <dc:creator>Ambuj M</dc:creator>
      <dc:date>2021-07-04T05:53:48Z</dc:date>
    </item>
    <item>
      <title>wireless packet flow explanation</title>
      <link>https://community.cisco.com/t5/wireless/wireless-packet-flow-explanation/m-p/2033758#M152804</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1. &lt;/P&gt;&lt;P&gt;client to AP ===&amp;gt; 802.11 frame.&lt;/P&gt;&lt;P&gt;AP to client ===&amp;gt; 802.11 frame. At AP, received wired side ethernet frame removes the ethernet header with tag and encapsulates the IP packet using 802.11 header with right Bssid for that vlan.&lt;/P&gt;&lt;P&gt;AP ethernet to switch interface ===&amp;gt; Tag/UnTag Ethernet frame. At AP, received 802.11 frames removes the 802.11 mac header, the inner packet will be used to encapsulate using ethernet frame with Tag based on received Bssid.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ARP request - Broadcast packet sent by wireless client to AP as unicast. Once it decapsulates the 802.11 header, the inner IP packet hits the wire on that broadcast domain to reach upstream wired switch and wireless on same AP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.&lt;/P&gt;&lt;P&gt;AP to WLC ===&amp;gt; capwap/lwapp. 802.11 packets are encapsulated on L3 IP-UDP.&lt;/P&gt;&lt;P&gt;WLC to AP ===&amp;gt; capwap/lwapp. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A style="color: #000000; font-size: 12px;"&gt;All the client (802.11) packets are encapsulated in a LWAPP packet by the LAP and sent to the WLC. WLC descapsulates the LWAPP packet and acts based on the destination IP address in the 802.11 packet. If the destination is one of the wireless clients associated to the WLC, it encapsulates the packet again with the LWAPP and sends it to the LAP of the client, where it is decapsulated and sent to the wireless client. If the destination is on the wired side of the network, it removes the 802.11 header, adds the Ethernet header, and forwards the packet to the connected switch, from where it is sent to the wired client. When a packet comes from the wired side, WLC removes the Ethernet header, adds the 802.11 header, encapsulates it with LWAPP, and sends it to the LAP, where it is decapsulated, and the 802.11 packet is delivered to the wireless client&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;check:-&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.cisco.com/message/3489064#3489064"&gt;https://supportforums.cisco.com/message/3489064#3489064&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.cisco.com/message/3717713#3717713"&gt;https://supportforums.cisco.com/message/3717713#3717713&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Oct 2012 00:10:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-packet-flow-explanation/m-p/2033758#M152804</guid>
      <dc:creator>Saravanan Lakshmanan</dc:creator>
      <dc:date>2012-10-23T00:10:55Z</dc:date>
    </item>
  </channel>
</rss>

