<?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 Packet Tracer WLC Issues in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/packet-tracer-wlc-issues/m-p/5022709#M267121</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;I've been trying to practice WLC configuration on packet tracer but for the life of me I cannot get it to work once having completed the initial configuration.&lt;/P&gt;
&lt;P&gt;I have tried the WLC-PT (which I can't get into even from the start) and am currently testing with WLC 3504. I have managed to get into it and set the WLC to have IP 192.168.99.5 and the link between it and my switch is a trunk with everything allowed. I also have a router connected to the switch which is trunking VLAN 99 (192.168.99.0/24) via a sub interface and my default VLAN (192.168.1.0/24).&lt;/P&gt;
&lt;P&gt;When I try to get to the WLC from my PC on VLAN 1 it just times out. I can't ping it from the PC, I can't ping it from the router, nothing.&lt;/P&gt;
&lt;P&gt;When looking in Simulation view, interVLAN works fine. The ping from PC1 goes over the access link to the switch, then to the router, at which point an ARP Request leaves the router with an 802.1Q tag of 99 and goes over the trunk from the switch to the WLC. This is where it's a bit weird. At the WLC when the ARP should be sent back to the switch, there is just a blank layer 2 PDU with the below inside:&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;5. The frame destination MAC address is not in the MAC table. The Wireless LAN Controller floods the frame to all ports in the same VLAN except the receiving port.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;Has anyone got any ideas? If you need anymore info then no problem.&lt;/P&gt;</description>
    <pubDate>Thu, 22 Feb 2024 15:57:03 GMT</pubDate>
    <dc:creator>PrimeYeti</dc:creator>
    <dc:date>2024-02-22T15:57:03Z</dc:date>
    <item>
      <title>Packet Tracer WLC Issues</title>
      <link>https://community.cisco.com/t5/wireless/packet-tracer-wlc-issues/m-p/5022709#M267121</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;I've been trying to practice WLC configuration on packet tracer but for the life of me I cannot get it to work once having completed the initial configuration.&lt;/P&gt;
&lt;P&gt;I have tried the WLC-PT (which I can't get into even from the start) and am currently testing with WLC 3504. I have managed to get into it and set the WLC to have IP 192.168.99.5 and the link between it and my switch is a trunk with everything allowed. I also have a router connected to the switch which is trunking VLAN 99 (192.168.99.0/24) via a sub interface and my default VLAN (192.168.1.0/24).&lt;/P&gt;
&lt;P&gt;When I try to get to the WLC from my PC on VLAN 1 it just times out. I can't ping it from the PC, I can't ping it from the router, nothing.&lt;/P&gt;
&lt;P&gt;When looking in Simulation view, interVLAN works fine. The ping from PC1 goes over the access link to the switch, then to the router, at which point an ARP Request leaves the router with an 802.1Q tag of 99 and goes over the trunk from the switch to the WLC. This is where it's a bit weird. At the WLC when the ARP should be sent back to the switch, there is just a blank layer 2 PDU with the below inside:&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;5. The frame destination MAC address is not in the MAC table. The Wireless LAN Controller floods the frame to all ports in the same VLAN except the receiving port.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;Has anyone got any ideas? If you need anymore info then no problem.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2024 15:57:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/packet-tracer-wlc-issues/m-p/5022709#M267121</guid>
      <dc:creator>PrimeYeti</dc:creator>
      <dc:date>2024-02-22T15:57:03Z</dc:date>
    </item>
    <item>
      <title>Re: Packet Tracer WLC Issues</title>
      <link>https://community.cisco.com/t5/wireless/packet-tracer-wlc-issues/m-p/5023453#M267202</link>
      <description>&lt;P&gt;For packet tracer questions best to post to &lt;A class="" href="https://learningnetwork.cisco.com/s/topic/0TO6e000000WEorGAG/packet-tracer" target="_blank" rel="nofollow noopener noreferrer"&gt;https://learningnetwork.cisco.com/s/topic/0TO6e000000WEorGAG/packet-tracer&lt;/A&gt; and also see &lt;A href="https://www.netacad.com/" target="_blank" rel="nofollow noopener noreferrer"&gt;https://www.netacad.com/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 23 Feb 2024 14:06:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/packet-tracer-wlc-issues/m-p/5023453#M267202</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2024-02-23T14:06:59Z</dc:date>
    </item>
    <item>
      <title>Re: Packet Tracer WLC Issues</title>
      <link>https://community.cisco.com/t5/wireless/packet-tracer-wlc-issues/m-p/5023458#M267203</link>
      <description>&lt;P&gt;Yes, there is issue with PT and wireless controllers; u may need to try different one; we had mentioned similar (if not the same issues).&amp;nbsp; search this site and CLN as well.&amp;nbsp;also see&amp;nbsp;&lt;A href="https://community.cisco.com/t5/wireless/packet-tracer-wlc-issue/m-p/4729563" target="_blank"&gt;https://community.cisco.com/t5/wireless/packet-tracer-wlc-issue/m-p/4729563&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;attach your PT file here in zip format.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards, ML&lt;BR /&gt;**Please Rate All Helpful Responses **&lt;/P&gt;</description>
      <pubDate>Fri, 23 Feb 2024 14:14:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/packet-tracer-wlc-issues/m-p/5023458#M267203</guid>
      <dc:creator>Martin L</dc:creator>
      <dc:date>2024-02-23T14:14:19Z</dc:date>
    </item>
  </channel>
</rss>

