<?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 CSCwn22565 - ERROR: cannot set default route for broadcast packets. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cscwn22565-error-cannot-set-default-route-for-broadcast-packets/m-p/5273196#M1120149</link>
    <description>&lt;P&gt;Hello Team,&lt;BR /&gt;in our environment we are running with Firepower 2110 with Cisco ASA having version 9.18.4.50.&lt;/P&gt;
&lt;P&gt;We have BGP peering between 2 different Sites and&amp;nbsp; one of the Site Core Switch also having BGP peering with Cisco ASA Firewall.&lt;BR /&gt;whenever BGP peering getting flap between Sites, all routes get refreshed, and it will also refreshed routes in Cisco ASA.&lt;BR /&gt;after that if we try to ping/traceroute Site IP address from Firewall, it is going to default route even though correct routes available in Cisco ASA Routing table&lt;BR /&gt;if we perform failover on Cisco ASA, all traffic towards cloud working perfectly fine.&lt;BR /&gt;Can anyone observe such behavior and is that related to given bug "CSCwn22565"&lt;/P&gt;</description>
    <pubDate>Wed, 19 Mar 2025 19:12:34 GMT</pubDate>
    <dc:creator>kunal-s-sawarkar</dc:creator>
    <dc:date>2025-03-19T19:12:34Z</dc:date>
    <item>
      <title>CSCwn22565 - ERROR: cannot set default route for broadcast packets.</title>
      <link>https://community.cisco.com/t5/network-security/cscwn22565-error-cannot-set-default-route-for-broadcast-packets/m-p/5273196#M1120149</link>
      <description>&lt;P&gt;Hello Team,&lt;BR /&gt;in our environment we are running with Firepower 2110 with Cisco ASA having version 9.18.4.50.&lt;/P&gt;
&lt;P&gt;We have BGP peering between 2 different Sites and&amp;nbsp; one of the Site Core Switch also having BGP peering with Cisco ASA Firewall.&lt;BR /&gt;whenever BGP peering getting flap between Sites, all routes get refreshed, and it will also refreshed routes in Cisco ASA.&lt;BR /&gt;after that if we try to ping/traceroute Site IP address from Firewall, it is going to default route even though correct routes available in Cisco ASA Routing table&lt;BR /&gt;if we perform failover on Cisco ASA, all traffic towards cloud working perfectly fine.&lt;BR /&gt;Can anyone observe such behavior and is that related to given bug "CSCwn22565"&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 19:12:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cscwn22565-error-cannot-set-default-route-for-broadcast-packets/m-p/5273196#M1120149</guid>
      <dc:creator>kunal-s-sawarkar</dc:creator>
      <dc:date>2025-03-19T19:12:34Z</dc:date>
    </item>
  </channel>
</rss>

