Global protect IP Query.

ArunKumar7 — Mon, 26 Feb 2024 13:52:00 GMT

So basically I have a windows machine connected to a router (which is my gateway), My win 10 Ip is 192.168.1.10 ad g/w Ip is 192.168.1.1.

Furthermore, my Router is connected to Palo Alto 10.0.0.1 is my IP, and 10.0.0.2 is my Palo interface IP. From the Windows 10 machine I am connected to the global protect using 10.0.0.2. Connection is established and my new GP ip is 172.16.1.10 also I can reach the server 100.100.100.2.

While pinging from my Windows machine to 100.100.100.2 I see the traffic is sent with the source IP 192.168.1.10 and destination as 100.100.100.2.
But why? It is supposed GP ip (172.16.1.10) why it is the same source IP? And also I see the packets are sent via UDP, not via SSL.

Can someone explain this, please?

Re: Global protect IP Query.

JayGolf — Wed, 28 Feb 2024 16:11:02 GMT

Hi @ArunKumar7 ,

I believe you have No direct access to local network unchecked. If you go to your Gateway config -> Split Tunnel -> Access Route -> "No direct access to local network". Having this unchecked means that you can access your local network via your physical adapter rather than GP. On the other hand, if you have this box checked, It restricts outgoing traffic on the local connected subnet. Instead of that traffic exiting through the local physical adapter like you would expect, the traffic is sent through the tunnel and (usually) dropped by the firewall.

topic Re: Global protect IP Query. in GlobalProtect Discussions

Global protect IP Query.

Re: Global protect IP Query.