<?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: Tunnel Traffic from ISP2 IP Working Despite Default Route on ISP1 – Need Insights? in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/tunnel-traffic-from-isp2-ip-working-despite-default-route-on/m-p/1237386#M6264</link>
    <description>&lt;P&gt;if both your ISP1 and ISP2 interfaces use the same zone, asymmetric routing is ignored&lt;/P&gt;</description>
    <pubDate>Fri, 05 Sep 2025 09:24:08 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2025-09-05T09:24:08Z</dc:date>
    <item>
      <title>Tunnel Traffic from ISP2 IP Working Despite Default Route on ISP1 – Need Insights?</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/tunnel-traffic-from-isp2-ip-working-despite-default-route-on/m-p/1237153#M6255</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;span class="lia-unicode-emoji" title=":repeat_button:"&gt;🔁&lt;/span&gt; Scenario Summary for &lt;STRONG&gt;Asymmetric routing&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;Primary ISP (ISP1): Default route with lower metric (10), so all traffic prefers this path.&lt;BR /&gt;Secondary ISP (ISP2): In Firewall, I manually initiate traffic using ping source &amp;lt;ISP2 IP&amp;gt; host 8.8.8.8.&lt;BR /&gt;Routing Table: Since 8.8.8.8 is unknown, the firewall uses the default route — which points to ISP1.&lt;BR /&gt;Result: Traffic goes out via ISP1, but the source IP is from ISP2. Return traffic will go to ISP2.&lt;BR /&gt;&lt;span class="lia-unicode-emoji" title=":warning:"&gt;⚠️&lt;/span&gt; Why This Might Not Work&lt;BR /&gt;This setup can cause asymmetric routing, where:&lt;/P&gt;
&lt;P&gt;Outbound traffic goes via ISP1.&lt;BR /&gt;Inbound traffic returns via ISP2.&lt;BR /&gt;This can lead to:&lt;/P&gt;
&lt;P&gt;Dropped packets due to stateful inspection (firewall sees return traffic on a different interface).&lt;BR /&gt;Routing inconsistencies unless properly handled.&lt;/P&gt;
&lt;HR /&gt;
&lt;H3&gt;&lt;span class="lia-unicode-emoji" title=":hammer_and_wrench:"&gt;🛠&lt;/span&gt;️ What Happens for the tunnel traffic in ISP-2&lt;/H3&gt;
&lt;P&gt;If we don’t add a static route for the remote peer public IP:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;The firewall uses the default route (ISP1).&lt;/LI&gt;
&lt;LI&gt;IKE traffic goes out via ISP1 with ISP2’s source IP.&lt;/LI&gt;
&lt;LI&gt;The return traffic comes to ISP2.&lt;/LI&gt;
&lt;LI&gt;The firewall drops the return traffic due to&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;asymmetric routing&lt;/STRONG&gt;.&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;&lt;span class="lia-unicode-emoji" title=":wrench:"&gt;🔧&lt;/span&gt;&lt;STRONG&gt;But tunnel traffic is still working, even though there is no static route configured for the peer's public IP.&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;&lt;STRONG&gt;Can someone break down the reason behind this?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Akash Thangavel&lt;/P&gt;</description>
      <pubDate>Wed, 03 Sep 2025 06:08:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/tunnel-traffic-from-isp2-ip-working-despite-default-route-on/m-p/1237153#M6255</guid>
      <dc:creator>AkashThangavel</dc:creator>
      <dc:date>2025-09-03T06:08:58Z</dc:date>
    </item>
    <item>
      <title>Re: Tunnel Traffic from ISP2 IP Working Despite Default Route on ISP1 – Need Insights?</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/tunnel-traffic-from-isp2-ip-working-despite-default-route-on/m-p/1237386#M6264</link>
      <description>&lt;P&gt;if both your ISP1 and ISP2 interfaces use the same zone, asymmetric routing is ignored&lt;/P&gt;</description>
      <pubDate>Fri, 05 Sep 2025 09:24:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/tunnel-traffic-from-isp2-ip-working-despite-default-route-on/m-p/1237386#M6264</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2025-09-05T09:24:08Z</dc:date>
    </item>
    <item>
      <title>Re: Tunnel Traffic from ISP2 IP Working Despite Default Route on ISP1 – Need Insights?</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/tunnel-traffic-from-isp2-ip-working-despite-default-route-on/m-p/1237387#M6265</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;Tom Piens,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are there any documents, and how is the tunnel still working even though it's in a different zone?&lt;/P&gt;</description>
      <pubDate>Fri, 05 Sep 2025 10:01:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/tunnel-traffic-from-isp2-ip-working-despite-default-route-on/m-p/1237387#M6265</guid>
      <dc:creator>AkashThangavel</dc:creator>
      <dc:date>2025-09-05T10:01:58Z</dc:date>
    </item>
    <item>
      <title>Re: Tunnel Traffic from ISP2 IP Working Despite Default Route on ISP1 – Need Insights?</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/tunnel-traffic-from-isp2-ip-working-despite-default-route-on/m-p/1237546#M6272</link>
      <description>&lt;P&gt;are you saying both ISP1 &amp;amp; ISP2 interfaces have a different zone?&lt;/P&gt;
&lt;P&gt;then you should review your security policy&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;is the tunnel responder or initiator?&lt;/P&gt;
&lt;P&gt;if you look at your session table, can you find the tunnel session and identify the interfaces (maybe also set up a flow basic capture to see which interfaces are really used)&lt;/P&gt;</description>
      <pubDate>Tue, 09 Sep 2025 09:19:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/tunnel-traffic-from-isp2-ip-working-despite-default-route-on/m-p/1237546#M6272</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2025-09-09T09:19:49Z</dc:date>
    </item>
  </channel>
</rss>

