<?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 GlobalProtect IPv6 findings in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-ipv6-findings/m-p/535441#M3816</link>
    <description>&lt;P&gt;With the IPv6 sinkholing feature not enabled, Mac and Windows users used to be able to successfully connect to IPv6 resources--seemingly completely bypassing GlobalProtect.&amp;nbsp; Then some Mac users reported not being able to connect to those IPv6 resources anymore.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The wisdom of allowing this IPv6 connectivity is of course debatable and it probably should be (will be eventually) sinkholed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyways, we tested some things and found that the connections worked on MacOS 13.0.1, but not on 13.2.&amp;nbsp; We did not test versions in between to figure out exactly where it broke.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;By adding a static route on the Mac the user was able to regain their IPv6 connectivity.&amp;nbsp; This static route was for ::/0 and pointed to the IPv6 gateway address of their Internet router.&amp;nbsp; This will break when they move networks but is a suitable workaround.&lt;/P&gt;</description>
    <pubDate>Wed, 22 Mar 2023 15:07:37 GMT</pubDate>
    <dc:creator>AaronAxvig</dc:creator>
    <dc:date>2023-03-22T15:07:37Z</dc:date>
    <item>
      <title>GlobalProtect IPv6 findings</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-ipv6-findings/m-p/535441#M3816</link>
      <description>&lt;P&gt;With the IPv6 sinkholing feature not enabled, Mac and Windows users used to be able to successfully connect to IPv6 resources--seemingly completely bypassing GlobalProtect.&amp;nbsp; Then some Mac users reported not being able to connect to those IPv6 resources anymore.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The wisdom of allowing this IPv6 connectivity is of course debatable and it probably should be (will be eventually) sinkholed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyways, we tested some things and found that the connections worked on MacOS 13.0.1, but not on 13.2.&amp;nbsp; We did not test versions in between to figure out exactly where it broke.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;By adding a static route on the Mac the user was able to regain their IPv6 connectivity.&amp;nbsp; This static route was for ::/0 and pointed to the IPv6 gateway address of their Internet router.&amp;nbsp; This will break when they move networks but is a suitable workaround.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Mar 2023 15:07:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-ipv6-findings/m-p/535441#M3816</guid>
      <dc:creator>AaronAxvig</dc:creator>
      <dc:date>2023-03-22T15:07:37Z</dc:date>
    </item>
  </channel>
</rss>

