<?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 C8200L contacting malicious IPs in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5544690#M312705</link>
    <description>&lt;P&gt;We have a C8200L on our network and the FortiGate 200F firewall has begun putting the C8200L into quarantine and blocking any access.&amp;nbsp; The FortiGate syslog show the C8200L srcip trying to contact several known malicious IPs.&amp;nbsp; dstinf=unknown-0&amp;nbsp; &amp;nbsp;action=deny&amp;nbsp; service=icmp/3/13&amp;nbsp; dstcountry=Netehrlands message="no protocol tuple found, drop."&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is the C8200L infected or could something else be going on?&amp;nbsp; Should it be rebuilt from Factory Default?&amp;nbsp; Thank you.&lt;/P&gt;</description>
    <pubDate>Fri, 10 Apr 2026 18:35:44 GMT</pubDate>
    <dc:creator>CRG_Defense_IT_Team</dc:creator>
    <dc:date>2026-04-10T18:35:44Z</dc:date>
    <item>
      <title>C8200L contacting malicious IPs</title>
      <link>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5544690#M312705</link>
      <description>&lt;P&gt;We have a C8200L on our network and the FortiGate 200F firewall has begun putting the C8200L into quarantine and blocking any access.&amp;nbsp; The FortiGate syslog show the C8200L srcip trying to contact several known malicious IPs.&amp;nbsp; dstinf=unknown-0&amp;nbsp; &amp;nbsp;action=deny&amp;nbsp; service=icmp/3/13&amp;nbsp; dstcountry=Netehrlands message="no protocol tuple found, drop."&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is the C8200L infected or could something else be going on?&amp;nbsp; Should it be rebuilt from Factory Default?&amp;nbsp; Thank you.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Apr 2026 18:35:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5544690#M312705</guid>
      <dc:creator>CRG_Defense_IT_Team</dc:creator>
      <dc:date>2026-04-10T18:35:44Z</dc:date>
    </item>
    <item>
      <title>Re: C8200L contacting malicious IPs</title>
      <link>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5544698#M312707</link>
      <description>&lt;P&gt;It's highly unlikely that the C8200L itself is "infected."&lt;/P&gt;&lt;P&gt;What you're seeing is almost always misattributed or misleading traffic.&lt;/P&gt;&lt;P&gt;The ICMP messages about an unreachable IP address are responses from the control plane, not proof of compromise.&lt;/P&gt;&lt;P&gt;What leads you to believe that these are suspicious IPs?&lt;/P&gt;</description>
      <pubDate>Fri, 10 Apr 2026 19:18:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5544698#M312707</guid>
      <dc:creator>aleabrahao</dc:creator>
      <dc:date>2026-04-10T19:18:24Z</dc:date>
    </item>
    <item>
      <title>Re: C8200L contacting malicious IPs</title>
      <link>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5544902#M312713</link>
      <description>&lt;P&gt;Glad to hear that the C8200L may not be infected.&amp;nbsp; Some of the IP which seem to trigger the quarantine are::&amp;nbsp; 91.196.152.12 (Onyphe Bot),&amp;nbsp; 137.184.105.192 , &amp;nbsp;45.156.129.54.&amp;nbsp; When I look them up they are reported on "Abuse" websites.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could the FortiGate firewall be responding to one of the addresses above probing the C8200L, and since the IP doesn't get through, responding 6 seconds later to a "dead" session?&amp;nbsp; Thanks.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Sun, 12 Apr 2026 16:49:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5544902#M312713</guid>
      <dc:creator>CRG_Defense_IT_Team</dc:creator>
      <dc:date>2026-04-12T16:49:41Z</dc:date>
    </item>
    <item>
      <title>Re: C8200L contacting malicious IPs</title>
      <link>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5544903#M312714</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/2064800"&gt;@CRG_Defense_IT_Team&lt;/a&gt;&amp;nbsp;did u tr to applay no ip unreachables cmd on ur outside-faicing int?&lt;/P&gt;</description>
      <pubDate>Sun, 12 Apr 2026 17:45:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5544903#M312714</guid>
      <dc:creator>Stefan Mihajlov</dc:creator>
      <dc:date>2026-04-12T17:45:05Z</dc:date>
    </item>
    <item>
      <title>Re: C8200L contacting malicious IPs</title>
      <link>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5545127#M312730</link>
      <description>&lt;P&gt;There's not an exact equivalent of no ip unreachable on the FortiGate, but great idea.&amp;nbsp; Thank you.&amp;nbsp; At this time, we believe the problem is the way the Check Quarantine Trigger in the Automation Stitches in the FortiGate firewall see the C8200L and applies a quarantine to the C8200L's MAC on the FortiSwitch port.&amp;nbsp; Thanks for all the ideas.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Apr 2026 18:25:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5545127#M312730</guid>
      <dc:creator>CRG_Defense_IT_Team</dc:creator>
      <dc:date>2026-04-13T18:25:37Z</dc:date>
    </item>
    <item>
      <title>Re: C8200L contacting malicious IPs</title>
      <link>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5546646#M312851</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/2064800"&gt;@CRG_Defense_IT_Team&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&amp;gt;&amp;nbsp;&lt;SPAN&gt;icmp/3/13&lt;BR /&gt;&lt;A href="https://www.iana.org/assignments/icmp-parameters/icmp-parameters.xhtml#icmp-parameters-codes-3" target="_blank" rel="noopener"&gt;https://www.iana.org/assignments/icmp-parameters/icmp-parameters.xhtml#icmp-parameters-codes-3&lt;/A&gt;&lt;BR /&gt;Type 3 — Destination Unreachable&lt;BR /&gt;13 Communication Administratively Prohibited [RFC1812]&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;This is the&amp;nbsp;C8200L replying to probes from your suspicious IPs.&amp;nbsp;&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1757654"&gt;@Stefan Mihajlov&lt;/a&gt;&amp;nbsp;suggestion is a good start.&amp;nbsp; The fact that you don't already have this configured suggests you have not followed standard good practice for a router which is exposed to the internet.&lt;BR /&gt;Take a look at&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/support/docs/ip/access-lists/13608-21.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/support/docs/ip/access-lists/13608-21.html&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;What would worry me though is if this router is behind a firewall already - why is the firewall allowing the suspicious IPs from the internet to attack the router?&amp;nbsp; I think you have a much bigger problem than just those logs - maybe somebody configured "permit ip any any" inbound from the internet on the firewall?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 19 Apr 2026 22:28:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5546646#M312851</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2026-04-19T22:28:19Z</dc:date>
    </item>
    <item>
      <title>Re: C8200L contacting malicious IPs</title>
      <link>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5546798#M312879</link>
      <description>&lt;P&gt;I need to change my email to&amp;nbsp;&lt;A href="mailto:sysadmins@crgrp.com" target="_blank"&gt;sysadmins@crgrp.com&lt;/A&gt;&amp;nbsp;to make sure our Network Admin is getting these messages also.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Apr 2026 14:01:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5546798#M312879</guid>
      <dc:creator>CRG_Defense_IT_Team</dc:creator>
      <dc:date>2026-04-20T14:01:27Z</dc:date>
    </item>
    <item>
      <title>Re: C8200L contacting malicious IPs</title>
      <link>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5546800#M312880</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;-&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/2064800"&gt;@CRG_Defense_IT_Team&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; It's connected to your cisco profile and therefore cannot be done&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;instantaneously ; contact &lt;A href="mailto:brodavie@cisco.com" target="_blank"&gt;brodavie@cisco.com&lt;/A&gt;&amp;nbsp;(commmunity manager) for more info&lt;/P&gt;
&lt;P&gt;&amp;nbsp; M.&lt;/P&gt;</description>
      <pubDate>Mon, 20 Apr 2026 14:07:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c8200l-contacting-malicious-ips/m-p/5546800#M312880</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2026-04-20T14:07:50Z</dc:date>
    </item>
  </channel>
</rss>

