topic Implications of "No direct Access to Local Network" toggle in Global protect client settings? in GlobalProtect Discussions

Implications of "No direct Access to Local Network" toggle in Global protect client settings?

darren_g — Sun, 29 Aug 2021 23:49:42 GMT

Hey folks.

I, like probably a lot of us these days, use Global protect for the major percentage of the company's workforce. I run split tunneling - internal resources go over the tunnel, anything else just uses the local internet.

Recently, I have had the need thrown at me the requirement to provide split tunneling for a set of addresses which are a dynamic DNS entry rather than fixed IP or subnet.

This seems to be perfect for adding into the "Domains and Applications' section of the client configuration - but after researching, I find this won't work without ticking the "No Direct access to Local Network" toggle.

Can anyone tell me the implications of doing this? Is it just the local interface network which can't be accessed while Global protect is running - or does this effectively make split tunneling useless by locking out anything except the tunnel?

I can't seem to find a definitive answer - it should just be what the wording says - lockout of the local LAN used to get internet access - but I've had situations where the logical interpretation of Palo Alto speak turns out to be not so logical before!

Thanks for any input

Re: Implications of "No direct Access to Local Network" toggle in Global protect client settings?

JoergSchuetter — Mon, 30 Aug 2021 06:17:49 GMT

Hello

Can you please point out where you read the constraints of "No direct access to Local Networks" in relation with "Domains and Applications".

On our systems "No direct access to Local Networks" is NOT ticked, but access to domain based destinations is configured (and it seems to work fine).

Re: Implications of "No direct Access to Local Network" toggle in Global protect client settings?

reaper — Mon, 30 Aug 2021 06:40:19 GMT

The 'domains and apps' section in split tunnelling does require a license, but the access to local network does not need to be enabled

The latter option prevents access to resources on the client's local interface subnet (home printers/Nas device,...) But local internet breakout and tunneled subnets will still be accessible

Re: Implications of "No direct Access to Local Network" toggle in Global protect client settings?

darren_g — Tue, 31 Aug 2021 00:27:54 GMT

It was a discussion or article I found on here (live community), from memory - I didn't save it, but if I can find it again, I will.

So if I simply add the domains I want into the domain based destinations, it should just work? Are the ports optional? or do I have to add them?

Re: Implications of "No direct Access to Local Network" toggle in Global protect client settings?

darren_g — Tue, 31 Aug 2021 00:34:57 GMT

I do have the Global protect license on the firewall, so that's not an issue.

I guess I'll just add the domains into the configuration and see what happens. Do you know if the port are optional, or if I have to include them?