<?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 Issue Routing Issues, no connection to 127.0.0.1, IPV6 on client causes connection issues, 5.2.X Client is awful in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-issue-routing-issues-no-connection-to-127-0-0-1/m-p/386395#M932</link>
    <description>&lt;P&gt;I have a multitude of issues I would love to see if anyone has solved.&lt;/P&gt;&lt;P&gt;With GlobalProtect 5.2.X routing works half the time and sometimes not at all. Reverting to 5.1.X solves this. However 5.1.X isn't compatible with Big Sur OSX. Help?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I have IPV6 enabled on clients traffic won't traverse the vpn. I have IPV6 disabled on the vpn as it is not implemented at the corporate office wan or lan as of yet. This is related to version 5.1.x or 5.2.x of the global protect client. How do I resolve this?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We also have developers that run content on local apache servers via 127.0.0.1 and once connected on global protect this fails. We aren't disabling local traffic while connected to the vpn so I don't understand this. Reverting to 5.1.X client fixes this. Again Big Sur isn't compatible with 5.1.X so this isn't a real fix. Any ideas?&lt;/P&gt;</description>
    <pubDate>Wed, 17 Feb 2021 15:36:53 GMT</pubDate>
    <dc:creator>itdaveramsey</dc:creator>
    <dc:date>2021-02-17T15:36:53Z</dc:date>
    <item>
      <title>GlobalProtect Issue Routing Issues, no connection to 127.0.0.1, IPV6 on client causes connection issues, 5.2.X Client is awful</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-issue-routing-issues-no-connection-to-127-0-0-1/m-p/386395#M932</link>
      <description>&lt;P&gt;I have a multitude of issues I would love to see if anyone has solved.&lt;/P&gt;&lt;P&gt;With GlobalProtect 5.2.X routing works half the time and sometimes not at all. Reverting to 5.1.X solves this. However 5.1.X isn't compatible with Big Sur OSX. Help?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I have IPV6 enabled on clients traffic won't traverse the vpn. I have IPV6 disabled on the vpn as it is not implemented at the corporate office wan or lan as of yet. This is related to version 5.1.x or 5.2.x of the global protect client. How do I resolve this?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We also have developers that run content on local apache servers via 127.0.0.1 and once connected on global protect this fails. We aren't disabling local traffic while connected to the vpn so I don't understand this. Reverting to 5.1.X client fixes this. Again Big Sur isn't compatible with 5.1.X so this isn't a real fix. Any ideas?&lt;/P&gt;</description>
      <pubDate>Wed, 17 Feb 2021 15:36:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-issue-routing-issues-no-connection-to-127-0-0-1/m-p/386395#M932</guid>
      <dc:creator>itdaveramsey</dc:creator>
      <dc:date>2021-02-17T15:36:53Z</dc:date>
    </item>
  </channel>
</rss>

