SSL VPN access to no public IP firewall that connection with S2S with public IP firewall

T.ZAKK — Wed, 18 Jun 2025 13:31:29 GMT

we have 5 firewalls , 1 have public IP we use ssl VPN,
the rest 4 FWs, they are connected to that 1 firewall with DPLC ,run S2S tunnel with private IP.
Now our SSL VPN user have only access to 1 public IP firewall LAN, but we want to access another 4 firewall's LAN as well

Re: SSL VPN access to no public IP firewall that connection with S2S with public IP firewall

BPry — Wed, 18 Jun 2025 17:55:20 GMT

@T.ZAKK,

If I'm understanding the issue properly this isn't a problem. You would just need to have the proper routing and security policies in place to facilitate the traffic to actually pass from your GlobalProtect clients to all of the rest of the firewall's connected resources. This means that your "public" firewall needs to have routes and security entries to facilitate access to everything else, but your "non-public" firewalls will also needs routes to know where to pass your GlobalProtect clients alongside their own rules to allow the traffic.

Hopefully that makes sense, but in short you'll just need to verify that everything is aware of the GlobalProtect subnets and routes them back to the "public" firewall and that everything is properly allowed from a security policy aspect across all firewalls.

topic SSL VPN access to no public IP firewall that connection with S2S with public IP firewall in GlobalProtect Discussions

SSL VPN access to no public IP firewall that connection with S2S with public IP firewall

Re: SSL VPN access to no public IP firewall that connection with S2S with public IP firewall