Add reference files

This commit is contained in:
2026-06-18 08:16:14 -05:00
parent c6e3095f26
commit 5202196f2d
8 changed files with 1487 additions and 0 deletions
@@ -0,0 +1,132 @@
<table class="table colsep rowsep table-striped">
<!--cq:include script="../../common/tablestack.jsp" /-->
<colgroup>
<col style="width: 25%" />
<col style="width: 75%" />
</colgroup>
<thead class="thead">
<tr class="row">
<th class="entry">
<div class="p">Issue ID</div>
</th>
<th class="entry">
<div class="p">Description</div>
</th>
</tr>
</thead>
<tbody class="tbody">
<tr class="row rowsep">
<td class="entry"><div class="p">GPC-26311</div></td>
<td class="entry relcol">
<div class="p">
Fixed an issue where GlobalProtect users were unable to submit Host
Information Profile (HIP) reports, which prevented security rules
requiring a HIP match from applying. This occurred when you connected
to an NGPA gateway using a dual-stack network, such as a mobile
hotspot. With this fix, GlobalProtect successfully submits HIP reports
regardless of your network configuration.
</div>
</td>
</tr>
<tr class="row rowsep">
<td class="entry"><div class="p">GPC-25946</div></td>
<td class="entry relcol">
<div class="p">
Fixed an issue where your GlobalProtect client did not send Host
Information Profile (HIP) check and report messages after you
established a connection to the gateway. This occurred even when a HIP
report was generated shortly before the connection, which could have
impacted security posture assessment. With this fix, your
GlobalProtect client now correctly sends HIP check and report messages
after establishing a connection.
</div>
</td>
</tr>
<tr class="row rowsep">
<td class="entry"><div class="p">GPC-25776</div></td>
<td class="entry relcol">
<div class="p">
Fixed an issue where GlobalProtect clients displayed an incorrect
"Connecting" status after a GlobalProtect Portal or Gateway
authentication failure, specifically when "Portal auth failed but
SAML/CAS auth is successful". This misleading status persisted even
though the connection had actually failed, preventing users from
understanding the true connection state.
</div>
</td>
</tr>
<tr class="row rowsep">
<td class="entry"><div class="p">GPC-25541</div></td>
<td class="entry relcol">
<div class="p">
Fixed an issue where MacOS GlobalProtect client version 6.2.8-416 was
unable to connect to the GlobalProtect gateway, getting stuck in a
connecting state.
</div>
</td>
</tr>
<tr class="row rowsep">
<td class="entry"><div class="p">GPC-25490</div></td>
<td class="entry relcol">
<div class="p">
(MacBook devices) Fixed an issue where your GlobalProtect enabled
device lost internet access after returning from hibernation. This
occurred when your computer completely lost network connectivity,
requiring a restart to restore internet access. With this fix, your
device maintains network connectivity after resuming from hibernation.
</div>
</td>
</tr>
<tr class="row rowsep">
<td class="entry"><div class="p">GPC-25394</div></td>
<td class="entry relcol">
<div class="p">
Fixed an issue where your traffic continued to pass through the
GlobalProtect tunnel interface after you disconnected GobalProtect,
preventing it from reverting to your local interface. With this fix,
your traffic properly reverts to the local interface after
GlobalProtect disconnects.
</div>
</td>
</tr>
<tr class="row rowsep">
<td class="entry"><div class="p">GPC-25320</div></td>
<td class="entry relcol">
<div class="p">
Fixed an issue where GlobalProtect intermittently appeared in the
foreground of your user session. This occurred even when you
configured GlobalProtect for on-demand connections and were not
actively trying to connect, causing it to overshadow other
applications. With this fix, GlobalProtect remains in the background
until you actively initiate a connection.
</div>
</td>
</tr>
<tr class="row rowsep">
<td class="entry"><div class="p">GPC-25280</div></td>
<td class="entry relcol">
<div class="p">
Fixed an issue where GlobalProtect clients on macOS devices would
intermittently get stuck in a "Connecting" state for several minutes
after waking from modern standby. This occurred due to a race
condition between DNS proxy reconfiguration and the VPN connection
process during wake from sleep, where the macOS DNS proxy would
temporarily stop and restart, causing the PanGPS service to time out
when attempting to send DNS configuration commands. This led to
repeated connection failures until the DNS proxy fully stabilized, a
condition that was exacerbated by the presence of multiple network
extensions on the macOS device.
</div>
</td>
</tr>
</tbody>
</table>